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
Unknown Object (File)
Sat, Apr 19, 3:28 PM
Unknown Object (File)
Sat, Apr 19, 11:45 AM
Unknown Object (File)
Sat, Apr 19, 11:41 AM
Unknown Object (File)
Sat, Apr 19, 11:37 AM
Unknown Object (File)
Sat, Apr 19, 11:12 AM
Unknown Object (File)
Mon, Apr 7, 8:15 PM
Unknown Object (File)
Mar 21 2025, 7:33 PM
Unknown Object (File)
Mar 8 2025, 11:29 PM
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