All of lore.kernel.org
 help / color / mirror / Atom feed
From: trondmy@kernel.org
To: Anna Schumaker <anna.schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] Export the NFSv4.1 'dacl' and 'sacl' attributes
Date: Sat, 14 May 2022 10:36:57 -0400	[thread overview]
Message-ID: <20220514143700.4263-1-trondmy@kernel.org> (raw)

From: Trond Myklebust <trond.myklebust@hammerspace.com>

This patch series allows the NFSv4 client to also export the NFSv4.1
'dacl' and 'sacl' attributes.
The main differences with respect to the existing NFSv4 'acl' attribute
are:

1) by splitting out the 'sacl' component, the server is free to enforce
   stronger privilege requirements against users that want to read or
   modify the sacl auditing features, while still allowing ordinary
   users to read and modify the 'dacl'.
2) Support for automatic inheritance of acls.

These two differences do mean that the acl tools will need some
modifications in order to make use of the new functionality.

Trond Myklebust (3):
  NFSv4: Specify the type of ACL to cache
  NFSv4: Add encoders/decoders for the NFSv4.1 dacl and sacl attributes
  NFSv4.1: Enable access to the NFSv4.1 'dacl' and 'sacl' attributes

 fs/nfs/nfs4proc.c       | 137 +++++++++++++++++++++++++++++++++-------
 fs/nfs/nfs4xdr.c        |  95 ++++++++++++++++++----------
 include/linux/nfs4.h    |   2 +
 include/linux/nfs_xdr.h |  10 +++
 4 files changed, 189 insertions(+), 55 deletions(-)

-- 
2.36.1


             reply	other threads:[~2022-05-14 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 14:36 trondmy [this message]
2022-05-14 14:36 ` [PATCH 1/3] NFSv4: Specify the type of ACL to cache trondmy
2022-05-14 14:36   ` [PATCH 2/3] NFSv4: Add encoders/decoders for the NFSv4.1 dacl and sacl attributes trondmy
2022-05-14 14:37     ` [PATCH 3/3] NFSv4.1: Enable access to the NFSv4.1 'dacl' and 'sacl' attributes trondmy

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=20220514143700.4263-1-trondmy@kernel.org \
    --to=trondmy@kernel.org \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.