public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@kernel.org>,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	Anna Schumaker <anna.schumaker@oracle.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [RFC PATCH 00/11] NFS/NFSD: nfs4_acl passthru for NFSv4 reexport
Date: Thu, 19 Feb 2026 18:07:40 -0500	[thread overview]
Message-ID: <aZeXvNclhMMzsweq@kernel.org> (raw)
In-Reply-To: <098b9502-8868-47c9-b164-be80bb11ae74@oracle.com>

On Thu, Feb 19, 2026 at 05:21:06PM -0500, Chuck Lever wrote:
> On 2/19/26 5:13 PM, Mike Snitzer wrote:
> > Hi,
> > 
> > This patchset aims to enable NFS v4.1 ACLs to be fully supported from
> > an NFS v4.1 client to an NFSD v4.1 export that reexports NFS v4.2
> > filesystem which has full support for NFS v4.1 ACLs (DACL and SACL).
> > 
> > The first 6 patches focus on nfs4_acl passthru enablement (primarily
> > for NFSD), patch 7 adds 4.1 nfs4_acl passthru support (DACL and SACL),
> > patch 8 optimizes particular nfs4_acl passthru implementation in NFSD
> > to skip memcpy if nfs4_acl passthru isn't needed, patches 9-11 offer
> > the corresponding required NFSv4 client changes.
> > 
> > This work is based on the NFS and NFSD code that has been merged
> > during the 7.0 merge window.
> > 
> > This patchset is marked as RFC because I expect there will be
> > suggestions for possible NFSD implementation improvements.
> 
> A couple of random observations:
> 
> 1. I haven't been a fan of these double-subsystem patch sets. Is there
> any way we can get this split into one set for NFSD and one for the NFS
> client, with as little code sharing between the two as possible? Maybe a
> pipe dream, I know.

Open to suggestions, but the reexport nature of this patchset makes it
tough for each half to be entirely standalone.

As is, patches 1 - 8 could all land via NFSD. But the code would be
dormant because no filesystems would set EXPORT_OP_NFSV4_ACL_PASSTHRU.

NFS _could_ just apply patch 3 (so it'd duplicate NFSD's commit for
patch 3) and then apply NFS patches 9 - 11.

> 2. Do you have a plan for similar passthru support for the NFSv4.2 POSIX
> draft ACL extension?

Wasn't on my radar, but I know you and Rick have been busy getting
NFSv4 POSIX draft ACL support to land in NFSD. I still have work ahead
to understand all that you guys landed... but being POSIX I just paid
attention to the mutual exclusion of your newer work versus nfs4_acl.

Excuse my naivety but doesn't NFSD now provide support for NFSv4.2
POSIX draft ACL extension? So what's the usecase you're thinking
passthru would be meaningful for?

If you might provide some guidance on expected work items that'd help
plant seeds. I can try to bone up on NFSv4.2 POSIX draft ACL extension
and we could discuss further at Bake-a-thon?

Relative to NFS v4.1 ACL passthru, Hammerspace needing to support 4.1
access for the benefit of kerberos usage made adding 4.1 ACL passthru
to 4.2 a compelling feature/requirement to implement.

Mike

  reply	other threads:[~2026-02-19 23:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19 22:13 [RFC PATCH 00/11] NFS/NFSD: nfs4_acl passthru for NFSv4 reexport Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 01/11] exportfs: add ability to advertise NFSv4 ACL passthru support Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 02/11] NFSD: factor out nfsd_supports_nfs4_acl() to nfsd/acl.h Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 03/11] NFS/NFSD: data structure enablement for nfs4_acl passthru support Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 04/11] NFSD: prepare to support SETACL nfs4_acl passthru Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 05/11] NFSD: add NFS4 reexport support for " Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 06/11] NFSD: add NFS4 reexport support for GETACL " Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 07/11] NFSD: add NFS4ACL_DACL and NFS4ACL_SACL passthru support Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 08/11] NFSD: avoid extra nfs4_acl passthru work unless needed Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 09/11] NFSv4: add reexport support for SETACL nfs4_acl passthru Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 10/11] NFSv4: add reexport support for GETACL " Mike Snitzer
2026-02-19 22:13 ` [RFC PATCH 11/11] NFSv4: set EXPORT_OP_NFSV4_ACL_PASSTHRU flag Mike Snitzer
2026-02-19 22:21 ` [RFC PATCH 00/11] NFS/NFSD: nfs4_acl passthru for NFSv4 reexport Chuck Lever
2026-02-19 23:07   ` Mike Snitzer [this message]
2026-02-20 15:46     ` Chuck Lever
2026-02-19 23:57   ` Trond Myklebust
2026-02-20 15:33     ` Chuck Lever
2026-02-22 17:53 ` Chuck Lever
2026-02-22 19:39   ` Mike Snitzer
2026-02-22 20:31     ` Chuck Lever

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=aZeXvNclhMMzsweq@kernel.org \
    --to=snitzer@kernel.org \
    --cc=anna.schumaker@oracle.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@hammerspace.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