Follow-up Comment #12, bug #33207 (project findutils):
Yes, POSIX is explicit that if a directory is modified during reading,
readdir() might return an entry zero times (the new entry was inserted prior
to the point where readdir is traversing) or more than once (adding an entry
reshuffled other entries, such that a previously read entry now falls after
the point where readdir is traversing); and it is made worse by the fact that
readdir is allowed to cache multiple entries rather than making a syscall on
ever readdir() call. That is, there is no atomicity with directory reading,
and portable apps have to be prepared for the worst.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?33207>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
