Bug 10374 - spurious "error reading current directory" errors
spurious "error reading current directory" errors
Product: Red Hat Linux
Classification: Retired
Component: cvs (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2000-03-27 14:05 EST by Jonathan Kamens
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-24 16:48:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch to initialize errno when necessary (2.02 KB, patch)
2000-03-27 14:09 EST, Jonathan Kamens
no flags Details | Diff

  None (edit)
Description Jonathan Kamens 2000-03-27 14:05:47 EST
Because readdir returns NULL when all directory entries have been read OR
there was an error reading the directory, cvs sets errno to 0 before each
call to readdir and then checks if it is non-zero afterwards to determine
if an error occurred.

Unfortunately, there are a few places in which cvs forgets to set errno to
0 when it should have, and as a result, it can sometimes report spurious
"error reading current directory" errors.  Yes, I actually saw this happen
once, although I can't replicate it easily in a small sample tree, and the
patch I'm about to attach to this bug does in fact make the spurious errors
I saw go away.

Y'all should submit this back to the cvs maintainers as well as putting it
into the redhat package until they incorporate it into the master tree.
Comment 1 Jonathan Kamens 2000-03-27 14:09:59 EST
Created attachment 162 [details]
patch to initialize errno when necessary
Comment 2 Jim Kingdon 2000-04-24 16:47:59 EDT
Some of these are already fixed in CVS 1.10.8, if memory serves.
Comment 3 Nalin Dahyabhai 2000-07-10 16:44:23 EDT
Slightly modified versions of these changes are being rolled into
cvs-1.10.8-7 and later.

Note You need to log in before you can comment on or make changes to this bug.