mwoehlke <[EMAIL PROTECTED]> writes:

> You are looking for this, yes?

Yes, that sort of thing.

>  10487 chmod    CALL  chmod(0x2800600,0x1a4)
>  10487 chmod    NAMI  "."
>  10487 chmod    RET   chmod 0
>  10487 chmod    CALL  chmod(0x2800600,0x1a4)
>  10487 chmod    NAMI  "b"
>  10487 chmod    RET   chmod 0
>  10487 chmod    CALL  close(0x1)
>  10487 chmod    RET   close 0
>  10487 chmod    CALL  exit(0)
>
> Does that look right?

No.  It looks like your kernel is busted.  The first chmod sets
the permissions of "." to 644, i.e., nobody can search it.
But the second chmod searches "." successfully.

Are you running this test as root?

> If I am reading 'man 2 chmod' right, the second chmod() is expected
> to fail with EACCES?

Yes, that's right.  It looks like your operating system is buggy.

Can you reproduce this bug with /bin/chmod?


_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils

Reply via email to