From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Marcel Ritter <ritter.marcel@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: RichACLs for BTRFS? (this time complete)
Date: Fri, 30 Oct 2015 07:08:23 -0400 [thread overview]
Message-ID: <56334FA7.9000606@gmail.com> (raw)
In-Reply-To: <CADurGxxzrqGs9E0HE4hqfk9KAz1o_RNRdeiF3TEVhiSGnzhChA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
On 2015-10-30 05:45, Marcel Ritter wrote:
> Hi btrfs-developers,
>
> I just read about the possible/planned merge of richacl patches into
> linux kernel 4.4.
>
> s. http://lwn.net/Articles/661078/
> s. http://lwn.net/Articles/661357/
>
> Will btrfs support richacls with kernel 4.4?
>
> According to the btrfs wiki, this topic has not been claimed:
>
> https://btrfs.wiki.kernel.org/index.php/Project_ideas#RichACLs_.2F_NFS4_ACLS
>
> As we'd like to use btrfs with NFSv4 I'd really like to see richacls on btrfs.
>
> Hope someone can comment on this topic.
>
While I don't think we'll directly support richacls, it shouldn't be
hard to integrate, as they're just stored in a couple of xattrs in the
'system' prefix. AFAICT, all that would really be needed is to make
sure that things are wired up correctly so that we can differentiate
between using POSIX ACL's and richacls (while I don't agree with a
number of choices the developers have made with richacls (It should be
relatively easy to find the long discussions we've had in the LKML
archives), I do agree that these two different models should not be mixed).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
prev parent reply other threads:[~2015-10-30 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 9:45 RichACLs for BTRFS? (this time complete) Marcel Ritter
2015-10-30 11:08 ` Austin S Hemmelgarn [this message]
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=56334FA7.9000606@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ritter.marcel@gmail.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;
as well as URLs for NNTP newsgroup(s).