RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Filed from caserun https://tcms.engineering.redhat.com/run/259740/#caserun_10787522

Version-Release number of selected component (if applicable):
rhel-7

Steps to Reproduce: 
strace -e trace=lstat,getxattr,lgetxattr ls -l /media 2>&1 |grep ^getxattr

Actual results: 
getxattr("/media", "system.posix_acl_access", 0x0, 0) = -1 ENODATA (No data available)
getxattr("/media", "system.posix_acl_default", 0x0, 0) = -1 ENODATA (No data available)


Expected results:
getxattr syscall should not be used


according to bug 720325 comment 32 it seems like a regression from RHEL6/coreutils-8.4-16.el6

Is this still an issue with kernels >= 3.1.0 ?
See bug 720325 comment 24

The fix for the issue was included in RHEL-6 only.  IIRC, it was rejected by gnulib upstream and we did not want to maintain it forever as a RHEL only fix.

Definitely _not_ a regression in RHEL-7.

Agree with Kamil, we don't want to diverge from upstream there. As pointed out by Pádraig, this syscall shouldn't be an issue with new kernels. Closing notabug unless there is real reason for changing this.