From: "Pali Rohár" <pali@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@kernel.org>, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfsd: Add support for mapping sticky bit into NFS4 ACL
Date: Sat, 5 Oct 2024 17:08:43 +0200 [thread overview]
Message-ID: <20241005150843.4ac6nugo7yusz2m6@pali> (raw)
In-Reply-To: <20240920192941.l2fomgmdfpwq7x6p@pali>
Hello Chuck, have you done more research on this as mentioned?
I think that this is really useful for non-POSIX clients as NFS4 ACLs
are not-POSIX; knfsd is already translating POSIX ACLs to non-POSIX
NFS4 ACLs, and this is just an improvement to covert also the
POSIX-sticky-bit in non-POSIX NFS4 ACL.
Also another improvement is that this change allows to modify all parts
of POSIX access mode (sticky bit, base mode permissions r/w/x and POSIX
ACL) via NFS4 ACL structure. So non-POSIX NFS4 client would be able to
add or remove directory sticky bit via NFS4 ACL editor.
Of course, nothing from this is required by RFC8881 specification, but
specification also does not disallow this for NFS4 servers. It is
improvement for non-POSIX clients. POSIX clients would of course not use
it.
next prev parent reply other threads:[~2024-10-05 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 22:15 [PATCH] nfsd: Add support for mapping sticky bit into NFS4 ACL Pali Rohár
2024-09-17 15:39 ` Chuck Lever
2024-09-17 16:10 ` Pali Rohár
2024-09-20 19:19 ` Chuck Lever
2024-09-20 19:29 ` Pali Rohár
2024-10-05 15:08 ` Pali Rohár [this message]
2024-10-05 15:40 ` Chuck Lever III
2024-10-06 6:19 ` Cedric Blancher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241005150843.4ac6nugo7yusz2m6@pali \
--to=pali@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--cc=tom@talpey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox