Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1240281 > unrolled thread

Re: [PATCH v9 00/43] Richacls

Started byPavel Machek <pavel@ucw.cz>
First post2015-10-06 11:10 +0200
Last post2015-10-07 15:50 +0200
Articles 5 — 4 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v9 00/43] Richacls Pavel Machek <pavel@ucw.cz> - 2015-10-06 11:10 +0200
    Re: [PATCH v9 00/43] Richacls Andreas Gruenbacher <agruenba@redhat.com> - 2015-10-06 14:50 +0200
      Re: [PATCH v9 00/43] Richacls James Morris <jmorris@namei.org> - 2015-10-07 09:40 +0200
        Re: [PATCH v9 00/43] Richacls Austin S Hemmelgarn <ahferroin7@gmail.com> - 2015-10-07 15:30 +0200
        Re: [PATCH v9 00/43] Richacls Andreas Gruenbacher <agruenba@redhat.com> - 2015-10-07 15:50 +0200

#1240281 — Re: [PATCH v9 00/43] Richacls

FromPavel Machek <pavel@ucw.cz>
Date2015-10-06 11:10 +0200
SubjectRe: [PATCH v9 00/43] Richacls
Message-ID<qgwpX-1Fi-13@gated-at.bofh.it>
On Mon 2015-10-05 21:36:27, Andreas Gruenbacher wrote:
> Here is another update of the richacl patch queue.  I would like to ask for
> feedback so that the core and ext4 code (patches 1-21) can be merged in the
> 4.4 merge window.  Changes since the last posting
> (https://lkml.org/lkml/2015/9/27/148):
> 
>  * A set_richacl inode operation similar to set_acl for POSIX ACLs was
>    added.  The filesystem specific code needed for adding richacl support
>    has shrunk: ext4_richacl_chmod, ext4_xattr_{list,get,set}_richacl,
>    ext4_init_richacl, ext4_richacl_xattr_handler were all replaced by vfs
>    functions.
> 
> The complete patch queue is available here:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/agruen/linux-richacl.git \
> 	richacl-2015-10-05
> 
> 
> The richacl user-space utilitites and test suite are available here:
> 
>   https://github.com/andreas-gruenbacher/richacl/
> 
> 
> We still have two open issues in nfs (see the previous posting) which don't
> affect the core functionality.

Should there be file in Documentation/ explaining how this works?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1240419

FromAndreas Gruenbacher <agruenba@redhat.com>
Date2015-10-06 14:50 +0200
Message-ID<qgzQR-6q5-19@gated-at.bofh.it>
In reply to#1240281
On Tue, Oct 6, 2015 at 11:07 AM, Pavel Machek <pavel@ucw.cz> wrote:
> Should there be file in Documentation/ explaining how this works?

There are plenty of comments in the code and in the patch descriptions
that describe how the code works. The user-space package has manual
pages that describe how to use richacls; this information would not be
accessible to users when put in Documentation/. Also, some background
information is available on http://www.bestbits.at/richacl/.

Thanks,
Andreas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1241199

FromJames Morris <jmorris@namei.org>
Date2015-10-07 09:40 +0200
Message-ID<qgRuq-6Ak-25@gated-at.bofh.it>
In reply to#1240419
On Tue, 6 Oct 2015, Andreas Gruenbacher wrote:

> On Tue, Oct 6, 2015 at 11:07 AM, Pavel Machek <pavel@ucw.cz> wrote:
> > Should there be file in Documentation/ explaining how this works?
> 
> There are plenty of comments in the code and in the patch descriptions
> that describe how the code works. The user-space package has manual
> pages that describe how to use richacls; this information would not be
> accessible to users when put in Documentation/. Also, some background
> information is available on http://www.bestbits.at/richacl/.

Are many distros planning on enabling this?  I gather RH is...


-- 
James Morris
<jmorris@namei.org>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1241484

FromAustin S Hemmelgarn <ahferroin7@gmail.com>
Date2015-10-07 15:30 +0200
Message-ID<qgWX7-65g-11@gated-at.bofh.it>
In reply to#1241199

[Multipart message — attachments visible in raw view] — view raw

On 2015-10-07 03:33, James Morris wrote:
> On Tue, 6 Oct 2015, Andreas Gruenbacher wrote:
>
>> On Tue, Oct 6, 2015 at 11:07 AM, Pavel Machek <pavel@ucw.cz> wrote:
>>> Should there be file in Documentation/ explaining how this works?
>>
>> There are plenty of comments in the code and in the patch descriptions
>> that describe how the code works. The user-space package has manual
>> pages that describe how to use richacls; this information would not be
>> accessible to users when put in Documentation/. Also, some background
>> information is available on http://www.bestbits.at/richacl/.
>
> Are many distros planning on enabling this?  I gather RH is...
>
I think a better question is "Are many distros planning on supporting 
this?".  Most distros probably won't enable this immediately, and many 
other than the enterprise ones are likely to put the choice on the 
system administrator.  I would expect that RHEL, OEL, and SLES (and by 
extension, Fedora, CentOS, and OpenSuSE) are likely to enable it, and 
Ubuntu might.  Gentoo will likely take the same approach as it does with 
xattrs and POSIX ACL's, namely that if you want them, you enable them 
yourself.  I would expect Arch to have support (probably within a week 
or two of this being merged), but not enable them by default, and I'd 
expect a similar policy from Debian.

[toc] | [prev] | [next] | [standalone]


#1241506

FromAndreas Gruenbacher <agruenba@redhat.com>
Date2015-10-07 15:50 +0200
Message-ID<qgXgt-6rH-7@gated-at.bofh.it>
In reply to#1241199
On Wed, Oct 7, 2015 at 9:33 AM, James Morris <jmorris@namei.org> wrote:
> Are many distros planning on enabling this?  I gather RH is...

It's a per-filesystem feature, so it's the admin's choice (if compiled
in). On ext4, you have to set the richacl feature flag to get Richacls
instead of POSIX ACLs.

Andreas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web