On Fri, Nov 04, Rob Landley wrote:
>
> That said, I'm pretty sure it's the old libc behavior that's defective. If a
So, what should the libc do? Reread the whole directory if it is changed? It
would be a nice DoS attack to just create and delete files and prevent others
from reading that directory.
IMHO it is the job of the filesystem implementation to allow correct SuSV3
specified directory reading.
Regards,
Jan Blunck
--
Jan Blunck [email protected]
SuSE LINUX AG - A Novell company
Maxfeldstr. 5 +49-911-74053-608
D-90409 Nürnberg http://www.suse.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
