Messages in this thread |  | | Date | Mon, 8 Dec 2025 17:56:01 +0800 | | Subject | [Question] nfsacl: why deny owner mode when deny user | | From | "zhangjian (CG)" <> |
| |
When user read bit is denied by nfs4_setfacl, owner read bit is also denied. Example:
[root@localhost ~]# nfs4_getfacl test/a # file: test/a A::OWNER@:rwatTcCy A::1000:rwatcy A::GROUP@:rtcy A::EVERYONE@:rtcy
[root@localhost ~]# nfs4_setfacl -a D::1000:r test/a [root@localhost ~]# nfs4_getfacl test/a # file: test/a D::OWNER@:r A::OWNER@:watTcCy D::1000:r A::1000:watcy A::GROUP@:rtcy A::EVERYONE@:rtcy
In function process_one_v4_ace, I see read bit is denied for owner: case ACL_USER: i = find_uid(state, state->users, ace->who); if (ace->type == NFS4_ACE_ACCESS_ALLOWED_ACE_TYPE) { allow_bits(&state->users->aces[i].perms, mask); } else { deny_bits(&state->users->aces[i].perms, mask); mask = state->users->aces[i].perms.deny; deny_bits(&state->owner, mask); } This change is commit in 09229ed. But I wonder why it is implemented like this.
|  |