Bug 2237410

Summary: getxattr() does not return ENOTSUP any longer for an invalid attribute
Product: [Fedora] Fedora Reporter: Ondrej <ondrej.valousek.xm>
Component: kernelAssignee: Jeff Layton <jlayton>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 39CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarod, jlayton, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-27 21:29:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ondrej 2023-09-05 11:34:34 UTC
On previous systems (i.e. RHEL-8) the following call:

getxattr ("name", XATTR_NAME_POSIX_ACL_ACCESS, NULL, 0);

resulted in setting errno to ENOTSUP if  "name" was a file on NFSv4 filesystem.
on Fedora 39, it sets errno to ENODATA instead.

Is this change intentional or it's a regression (most likely).

Related thread:
https://lists.gnu.org/archive/html/bug-gnulib/2023-04/msg00228.html

Reproducible: Always

Steps to Reproduce:
Happens every time



Reproducible: Always

Comment 1 Aoife Moloney 2024-11-27 21:29:01 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.