scanner: don't skip directory entries with type DT_UNKNOWN
#2703
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the readdir(2) man-page, not all file-systems support returning the entry's file-type in
d_type
. For example, the reprotest reproducibility tool, uses the disorderfs FUSE file-system to shuffle the order in which directory entries are returned, and this does not setd_type
. Therefore, in addition to entries with typeDT_DIR
andDT_LNK
, also process entries with typeDT_UNKNOWN
.For example, install disorderfs:
Mount mu over it:
Build mu:
Then run the test-suite:
In both cases, scanning testdir2 returned no entries, e.g.:
Here's an example Debian CI test failure: https://salsa.debian.org/emacsen-team/maildir-utils/-/jobs/5635549