Re: [BUG] Generic syscalls -- chmod vs. fchmodat

From: Roland McGrath
Date: Mon Jan 24 2011 - 16:05:47 EST

POSIX says "A null pathname shall not be successfully resolved." This
applies to relative pathnames too, and a file name argument to an *at
function using AT_FDCWD is a relative pathname. So I think there is no
situation at all in which the empty string should resolve to anything.
It's generally in the domain of the kernel to enforce these kinds of rules,
so I think that having the kernel fail with ENOENT for all empty-string
cases is the right thing to do.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at