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)
Dec 10 2024, 7:54 AM
Unknown Object (File)
Nov 30 2024, 2:00 AM
Unknown Object (File)
Nov 30 2024, 2:00 AM
Unknown Object (File)
Nov 30 2024, 1:59 AM
Unknown Object (File)
Nov 27 2024, 3:07 AM
Unknown Object (File)
Nov 26 2024, 12:12 PM
Unknown Object (File)
Nov 25 2024, 11:29 AM
Unknown Object (File)
Nov 22 2024, 6:40 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