Bug 1265950 - ls -l uses getxattr (regression of bug 720325)
ls -l uses getxattr (regression of bug 720325)
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: coreutils (Show other bugs)
Unspecified Linux
unspecified Severity unspecified
: rc
: ---
Assigned To: Ondrej Vasik
Depends On:
  Show dependency treegraph
Reported: 2015-09-24 04:22 EDT by Karel Volný
Modified: 2015-10-18 17:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-10-18 17:37:46 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Karel Volný 2015-09-24 04:22:01 EDT
Filed from caserun https://tcms.engineering.redhat.com/run/259740/#caserun_10787522

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

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
Comment 2 Pádraig Brady 2015-09-24 08:02:05 EDT
Is this still an issue with kernels >= 3.1.0 ?
See bug 720325 comment 24
Comment 3 Kamil Dudka 2015-09-24 14:15:00 EDT
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.
Comment 4 Ondrej Vasik 2015-10-18 17:37:46 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.