Bug 2059052
| Summary: | [RHEL9 Beta] nfs4_setfacl fails on numeric name file with error: "No path(s) specified." | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Ju Ke <jke> |
| Component: | nfs4-acl-tools | Assignee: | Steve Dickson <steved> |
| Status: | CLOSED ERRATA | QA Contact: | Yongcheng Yang <yoyang> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 9.2 | CC: | xzhou |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | nfs4-acl-tools-0.4.2-0.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-09 08:20:22 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2025486 | ||
|
Description
Ju Ke
2022-02-28 04:20:23 UTC
Quote from https://bugzilla.redhat.com/show_bug.cgi?id=2023135#c9 (In reply to J. Bruce Fields from comment #9) > The problem is that a number there has a special meaning; from the > nfs4_setfacl man page: > > -a acl_spec [index] > add the ACEs from acl_spec to file's ACL. ACEs are inserted > starting at the indexth position (DEFAULT: 1) of file's ACL. > > So in the case the next word after acl_spec is a number, it's ambiguous > whether it was meant to be an index or a file name. > > Well, actually, I think a file is mandatory, so in the case of "nfs4_setfacl > -a A::OWNER@:rwatTcCy 123", "123" has to be a file name. But it's also > legal to specify multiple filenames, so e.g. "nfs4_setfacl -a > A::OWNER@:rwatTcCy 123 file.txt" will always be ambiguous. > > For now, either "nfs4_setfacl -a A::OWNER@:rwatTcCy ./123" or "nfs4_setfacl > -a A::OWNER@:rwatTcCy 1 123" is a workaround. > > Longer term, this syntax is inherently ambiguous, so we should replace it by > something else and phase it out. This may need to be fixed upsream firstly. Verified this issue fixed in latest version: [root@ibm-x3650m4-08 mnt_test]# nfs4_getfacl 123 # file: 123 A::OWNER@:rwatTcCy A::GROUP@:rtcy A::EVERYONE@:rtcy [root@ibm-x3650m4-08 mnt_test]# nfs4_setfacl -a A::EVERYONE@:RWX 123 <<<< [root@ibm-x3650m4-08 mnt_test]# nfs4_getfacl 123 # file: 123 A::OWNER@:rwaxtTcCy A::GROUP@:rwaxtcy A::EVERYONE@:rwaxtcy [root@ibm-x3650m4-08 mnt_test]# rpm -q nfs4-acl-tools nfs4-acl-tools-0.4.2-0.el9.x86_64 [root@ibm-x3650m4-08 mnt_test]# ################################### ### Compared with previous version: ################################### [root@ci-vm-10-0-137-206 mnt_test]# rpm -q nfs4-acl-tools nfs4-acl-tools-0.3.5-8.el9.x86_64 [root@ci-vm-10-0-137-206 mnt_test]# nfs4_getfacl 123 # file: 123 A::OWNER@:rwatTcCy A::GROUP@:rtcy A::EVERYONE@:rtcy [root@ci-vm-10-0-137-206 mnt_test]# nfs4_setfacl -a A::EVERYONE@:RWX 123 No path(s) specified. <<<<<<<<<<<<<< [root@ci-vm-10-0-137-206 mnt_test]# nfs4_setfacl -a A::EVERYONE@:RWX ./123 [root@ci-vm-10-0-137-206 mnt_test]# nfs4_getfacl 123 # file: 123 A::OWNER@:rwaxtTcCy A::GROUP@:rwaxtcy A::EVERYONE@:rwaxtcy [root@ci-vm-10-0-137-206 mnt_test]# 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 (nfs4-acl-tools 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-2023:2520 |