lkml.org 
[lkml]   [1999]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [RFC] Bug in mkdir(2)
Date
   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/

\
 
 \ /
  Last update: 2005-03-22 13:52    [W:0.588 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site