Bug 1982608
Summary: | glibc: Fix glob() implementation on XFS [rhel-8.7.0] | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Michal Kolar <mkolar> |
Component: | glibc | Assignee: | DJ Delorie <dj> |
Status: | CLOSED ERRATA | QA Contact: | Martin Coufal <mcoufal> |
Severity: | unspecified | Docs Contact: | Jacob Taylor Valdez <jvaldez> |
Priority: | unspecified | ||
Version: | 8.6 | CC: | ashankar, codonell, dj, fweimer, jvaldez, mcoufal, mnewsome, pfrankli, sipoyare, skolosov |
Target Milestone: | beta | Keywords: | Bugfix, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glibc-2.28-200.el8 | Doc Type: | Bug Fix |
Doc Text: |
.Wildcard functions in Makefiles no longer return symbolic links when only directories are expected
Previously, the `GLOB_ONLYDIR` hint used by `glob()` misreported symbolic links as directories on certain XFS filesystems. When using `glob()`, `make` did not confirm that the hints were actually directories and, as a result, wildcard functions in Makefiles returned symbolic links when only directories were expected.
The bug has been fixed and wildcard functions in Makefiles no longer return symbolic links when only directories are expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-08 10:43:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Kolar
2021-07-15 09:32:22 UTC
This seems to be due to a limitation on XFS filesystems - the getdents syscall doesn't reliably fill in the entry types. Running on ext4 or tmpfs filesystems works fine. It might also be a glibc bug, as glob() relies on these unreliable entry types, and returns mismatched results. This has been identified as a glibc bug, see https://sourceware.org/pipermail/libc-alpha/2021-August/129910.html This bug does not qualify for a fix at 7.9's current point in its lifecycle, moving it to 8.6 for consideration. Note that as a workaround, using a non-XFS filesystem (such as EXT4) avoids this bug. Note that this bug only happens on XFS filesystems that are created with "mkfs.xfs -m crc=0 -n ftype=0 ...". These used to be the defaults, but no longer are. "man mkfs.xfs" will tell you if crc=1 (which forces ftype=1) is the default for your version. Setting crc=1 or ftype=1 when creating the filesystem bypasses the bug, but is (for obvious reasons ;) not considered a viable workaround. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (glibc bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:7684 |