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  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" <>
To:	Theodore Tso <>,
	Jörn Engel <>,
	"H. Peter Anvin" <>,
	Christoph Hellwig <>,
	Ulrich Drepper <>,
	Linux Kernel Mailing List <>,
	Neil Brown <>
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.)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists