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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: If not readdir() then what?
    ... after closing the directory stream using closedir() and then reopening ... I would definitely argue that an application ... Joern thought that rm -rf might relying on the telldir cookie ...
    (Linux-Kernel)
  • Re: If not readdir() then what?
    ... Garbage-collecting them on closedir() does not work. ... but there seem to be applications that keep the telldir() cookie ... It doesn't state explicitly that you can use the telldir cookie() ... programmer would be very ill-advised to rely on this working. ...
    (Linux-Kernel)
  • Re: telldir()/seekdir() confusion
    ... DN>> seekdir(dirp, pos); ... DN> I don't think there's any pstandard that says that telldir has to ... "If the most recent operation on the directory stream was a seekdir(), ...
    (freebsd-hackers)