Re: *at syscalls for xattrs?

[Jeff Garzik <jeff@garzik.org>]

H. Peter Anvin wrote:
> Miklos Szeredi wrote:
> > The *at() thing basically gives you the advantages of a CWD without
> > the disadvantages.
> >
> > For example it could be useful to implement the functionality of
> > find(1) as a library interface.
> What the *at() interfaces really do is fix/paper over a longstanding
> wart in Unix: the cwd really should have been a standard file descriptor
> (like stdin/stdout/stderr) instead of a magic piece of state maintained
> in kernel space.
It's more than a wart, IMO.  *at() allows one to close races (with 
potential security implications) that are otherwise impossible to close, 
in directory traversal.
*at() permits a userspace program to hold proper references to all 
objects during a directory traversal, with all that implies.
	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/