From: Steve Dickson <steved@redhat.com>
To: trondmy@kernel.org, "J.Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/6] Allow nfs4-acl-tools to access 'dacl' and 'sacl'
Date: Tue, 21 Jun 2022 09:43:44 -0400 [thread overview]
Message-ID: <b070ad50-08d7-a967-21f5-ecfbbd7105d9@redhat.com> (raw)
In-Reply-To: <20220514144436.4298-1-trondmy@kernel.org>
On 5/14/22 10:44 AM, trondmy@kernel.org wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
>
> The following patch set matches the kernel patches to allow access to
> the NFSv4.1 'dacl' and 'sacl' attributes. The current patches are very
> basic, adding support for encoding/decoding the new attributes only when
> the user specifies the '--dacl' or '--sacl' flags on the command line.
>
> Trond Myklebust (6):
> libnfs4acl: Add helpers to set the dacl and sacl
> libnfs4acl: Add support for the NFS4.1 ACE_INHERITED_ACE flag
> The NFSv41 DACL and SACL prepend an extra field to the acl
> nfs4_getacl: Add support for the --dacl and --sacl options
> nfs4_setacl: Add support for the --dacl and --sacl options
> Edit manpages to document the new --dacl, --sacl and inheritance
> features
>
> include/libacl_nfs4.h | 18 +++++++
> include/nfs4.h | 6 +++
> libnfs4acl/Makefile | 2 +
> libnfs4acl/acl_nfs4_copy_acl.c | 2 +
> libnfs4acl/acl_nfs4_xattr_load.c | 14 +++++-
> libnfs4acl/acl_nfs4_xattr_pack.c | 22 ++++++--
> libnfs4acl/nfs4_ace_from_string.c | 3 ++
> libnfs4acl/nfs4_get_ace_flags.c | 2 +
> libnfs4acl/nfs4_getacl.c | 84 +++++++++++++++++++++++++++++++
> libnfs4acl/nfs4_new_acl.c | 1 +
> libnfs4acl/nfs4_setacl.c | 49 ++++++++++++++++++
> man/man1/nfs4_getfacl.1 | 14 ++++++
> man/man1/nfs4_setfacl.1 | 8 +++
> man/man5/nfs4_acl.5 | 10 ++++
> nfs4_getfacl/nfs4_getfacl.c | 73 ++++++++++++++++++++++++---
> nfs4_setfacl/nfs4_setfacl.c | 67 ++++++++++++++++++++++--
> 16 files changed, 359 insertions(+), 16 deletions(-)
> create mode 100644 libnfs4acl/nfs4_getacl.c
> create mode 100644 libnfs4acl/nfs4_setacl.c
>
My apologies this took so long....
Committed (tag: nfs4-acl-tools-0.4.1-rc)
steved.
next prev parent reply other threads:[~2022-06-21 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 14:44 [PATCH 0/6] Allow nfs4-acl-tools to access 'dacl' and 'sacl' trondmy
2022-05-14 14:44 ` [PATCH 1/6] libnfs4acl: Add helpers to set the dacl and sacl trondmy
2022-05-14 14:44 ` [PATCH 2/6] libnfs4acl: Add support for the NFS4.1 ACE_INHERITED_ACE flag trondmy
2022-05-14 14:44 ` [PATCH 3/6] The NFSv41 DACL and SACL prepend an extra field to the acl trondmy
2022-05-14 14:44 ` [PATCH 4/6] nfs4_getacl: Add support for the --dacl and --sacl options trondmy
2022-05-14 14:44 ` [PATCH 5/6] nfs4_setacl: " trondmy
2022-05-14 14:44 ` [PATCH 6/6] Edit manpages to document the new --dacl, --sacl and inheritance features trondmy
2022-05-15 1:59 ` [PATCH 0/6] Allow nfs4-acl-tools to access 'dacl' and 'sacl' J.Bruce Fields
2022-05-15 3:23 ` Trond Myklebust
2022-05-19 13:47 ` Steve Dickson
2022-05-19 13:53 ` bfields
2022-05-19 18:52 ` Steve Dickson
2022-05-19 19:01 ` bfields
2022-06-21 13:43 ` Steve Dickson [this message]
2022-06-21 13:58 ` J.Bruce Fields
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=b070ad50-08d7-a967-21f5-ecfbbd7105d9@redhat.com \
--to=steved@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).