Page MenuHomeFreeBSD

fts_read: Handle error from a NULL return better.
ClosedPublic

Authored by bdrewery on Nov 11 2020, 11:42 PM.
Tags
None
Referenced Files
F103120230: D27184.diff
Thu, Nov 21, 6:54 AM
Unknown Object (File)
Tue, Nov 19, 10:54 AM
Unknown Object (File)
Sun, Nov 10, 4:19 AM
Unknown Object (File)
Thu, Nov 7, 4:34 AM
Unknown Object (File)
Fri, Oct 25, 4:35 AM
Unknown Object (File)
Fri, Oct 25, 4:34 AM
Unknown Object (File)
Fri, Oct 25, 4:34 AM
Unknown Object (File)
Fri, Oct 25, 4:25 AM
Subscribers

Details

Summary

This is addressing cases such as fts_read(3) encountering an [EIO]
from fchdir(2) when FTS_NOCHDIR is not set. That would otherwise be
seen as a successful traversal in some of these cases while silently
discarding expected work.

As noted in r264201, fts_read() does not set errno to 0 on a successful
EOF so it needs to be set before calling it. Otherwise we might see
a random error from one of the iterations.

gzip is ignoring most errors and could be improved separately.

Sponsored by: Dell EMC

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable