public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Anna Schumaker <anna.schumaker@oracle.com>
To: rick.macklem@gmail.com, linux-nfs@vger.kernel.org
Cc: Rick Macklem <rmacklem@uoguelph.ca>
Subject: Re: [PATCH v2 7/8] Set SB_POSIXACL if the server supports the extension
Date: Mon, 5 Jan 2026 17:00:34 -0500	[thread overview]
Message-ID: <a4b591f9-5240-4aaa-9022-bfa4b8dc37ac@oracle.com> (raw)
In-Reply-To: <20260103234033.1256-8-rick.macklem@gmail.com>

Hi Rick,

On 1/3/26 6:40 PM, rick.macklem@gmail.com wrote:
> From: Rick Macklem <rmacklem@uoguelph.ca>
> 
> Check to see if both the POSIX draft default ACL and
> POSIX draft access ACL are supported by the server.
> If so, set SB_POSIXACL.
> 
> Signed-off-by: Rick Macklem <rmacklem@uoguelph.ca>
> ---
>  fs/nfs/super.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> index 57d372db03b9..aa0f53c3d01d 100644
> --- a/fs/nfs/super.c
> +++ b/fs/nfs/super.c
> @@ -1352,6 +1352,11 @@ int nfs_get_tree_common(struct fs_context *fc)
>  		goto error_splat_super;
>  	}
>  
> +	/* Set SB_POSIXACL if the server supports the NFSv4.2 extension. */
> +	if ((server->attr_bitmask[2] & FATTR4_WORD2_POSIX_DEFAULT_ACL) &&
> +	    (server->attr_bitmask[2] & FATTR4_WORD2_POSIX_ACCESS_ACL))
> +		s->s_flags |= SB_POSIXACL;

Just a heads up that server->attr_bitmask only exists if the kernel is configured
with CONFIG_NFS_V4=y, so the compiler will complain about this:

fs/nfs/super.c:1348:15: error: no member named 'attr_bitmask' in 'struct nfs_server'
 1348 |         if ((server->attr_bitmask[2] & FATTR4_WORD2_POSIX_DEFAULT_ACL) &&
      |              ~~~~~~  ^
fs/nfs/super.c:1349:15: error: no member named 'attr_bitmask' in 'struct nfs_server'
 1349 |             (server->attr_bitmask[2] & FATTR4_WORD2_POSIX_ACCESS_ACL))
      |              ~~~~~~  ^
2 errors generated.

You'll probably need to either move it into NFS v4 specific code or hide it behind
and #ifdef.

Thanks,
Anna

> +
>  	s->s_flags |= SB_ACTIVE;
>  	error = 0;
>  


  reply	other threads:[~2026-01-05 22:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-03 23:40 [PATCH v2 0/8] Add NFSv4.2 POSIX ACL support to the client rick.macklem
2026-01-03 23:40 ` [PATCH v2 1/8] Add definitions for the POSIX draft ACL attributes rick.macklem
2026-01-03 23:40 ` [PATCH v2 2/8] Add entries to the predefined client operations enum rick.macklem
2026-01-03 23:40 ` [PATCH v2 3/8] Add new entries for handling POSIX draft ACLs rick.macklem
2026-01-03 23:40 ` [PATCH v2 4/8] Make posix_acl_from_nfsacl() global rick.macklem
2026-01-03 23:40 ` [PATCH v2 5/8] Make three functions global and move them to acl.c rick.macklem
2026-01-03 23:40 ` [PATCH v2 6/8] Make nfs4_server_supports_acls() global rick.macklem
2026-01-03 23:40 ` [PATCH v2 7/8] Set SB_POSIXACL if the server supports the extension rick.macklem
2026-01-05 22:00   ` Anna Schumaker [this message]
2026-01-05 23:56     ` Rick Macklem
2026-01-03 23:40 ` [PATCH v2 8/8] Add support for the NFSv4.2 POSIX draft ACL attributes rick.macklem
  -- strict thread matches above, loose matches on Subject: below --
2026-01-14  1:01 [PATCH v2 7/8] Set SB_POSIXACL if the server supports the extension rick.macklem

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=a4b591f9-5240-4aaa-9022-bfa4b8dc37ac@oracle.com \
    --to=anna.schumaker@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rick.macklem@gmail.com \
    --cc=rmacklem@uoguelph.ca \
    /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