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, Sep 5, 10:23 AM
Unknown Object (File)
Sat, Sep 5, 3:15 AM
Unknown Object (File)
Fri, Sep 4, 7:40 PM
Unknown Object (File)
Thu, Sep 3, 1:03 PM
Unknown Object (File)
Thu, Sep 3, 3:30 AM
Unknown Object (File)
Tue, Sep 1, 4:15 AM
Unknown Object (File)
Tue, Sep 1, 3:03 AM
Unknown Object (File)
Mon, Aug 31, 2:36 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