linux-kernel - Re: If not readdir() then what?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 08 Apr 2007 12:28:32 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Theodore Tso <tytso@....edu>,
	Jörn Engel <joern@...ybastard.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Christoph Hellwig <hch@...radead.org>,
	Ulrich Drepper <drepper@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Neil Brown <neilb@...e.de>
Subject: Re: If not readdir() then what?

Theodore Tso wrote:
> It doesn't state explicitly that you can use the telldir cookie()
> after closing the directory stream using closedir() and then reopening
> it using opendir(), but given that it states that results are
> undefined after a rewinddir() --- which is much less violent than a
> closedir()/opendir(), I would definitely argue that an application
> programmer would be very ill-advised to rely on this working.
> 
> (Of course, I'd argue that an application programmer shouldn't use
> telldir/seekdir at all.....)
> 
> Ulrich, is it too late to insert a clarification that the telldir()
> cookie isn't guaranteed to be valid after closedir() *or* rewinddir()?

More fundamentally, the telldir cookie should never be valid when 
applied to a different DIR * (even one that refers to the same directory.)

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