> News:
>
>
> It is my first time to look into the kernel code :(
> There are some errors when I run 'attr -l juer' --- ' attr_list: Bad
> address'. It seemed that the error is occured when calling function
> __user_walk(...) ( sys_attrctl --> user_path_walk )
>
> int __user_walk(const char *name, unsigned flags, struct nameidata *nd)
> {
> char *tmp;
> int err;
>
> tmp = getname(name);
> err = PTR_ERR(tmp);
>
> /* Debug */
> if( err == -14)
> printk("Attr Debug 1: Bad address!\n");
>
> if (!IS_ERR(tmp)) {
> err = 0;
> if (path_init(tmp, flags, nd))
> err = path_walk(tmp, nd);
>
> /* Debug */
> if( err == -14)
> printk("Attr Debug 1: Bad address!\n");
>
> putname(tmp);
> }
> return err;
> }
>
> I saw the error message "Attr Debug 1:Bad address!" when I ran that
> command.
> Did any expert :) meet this similar problem?
>
> Juer
>
Hi Juer,
This has come up before when Thomas Graichen was trying to get attrctl
working on PowerPC. My best guess at the time was that it was something
todo with the structure passed into the attrctl syscall doing something
funny on ppc. Check out the list archive around 7 Dec 2001, I'll attach the
last post I sent Thomas. We needed a few printk's added to check what
was happening.
Andrew
--
Andrew Gildfind - R&D Software Engineer - SGI Melbourne Australia
email: ajag@xxxxxxx - work: +61.3.9834.8200 mobile: 0412.834.183
ppc
Description: Text document
|