Messages in this thread | | | From | Douglas Weimer <> | Subject | Re: [RFC] Bug in mkdir(2) | Date | Wed, 16 Jun 1999 16:59:10 -0400 (EDT) |
| |
Following symlinks can be useful at times. It is the root-owned processes responsibility to check for symlinks in /tmp. This argument can be used for any file manipulation in a globally writable directory. Both mkdir("foo") and mkdir("foo/") should follow symlinks for consistency purposes.
Doug
> > The same as for mkdir("foo")? mkdir behaves like open( ,O_CREAT|O_EXCL, ); > Which doesn't follow links, by exactly the same reasons. Think of > ln -sf <something_interesting_that_should_not_exist> /tmp/foo012345 > when root-owned process is expected to create/mkdir/mknod/rename to > /tmp/foo12345. > > Just to clarify: mkdir("foo") doesn't follow the link. mkdir("foo/") does. > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/ >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |