linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "James Johnston" <johnstonj.public@codenest.com>
To: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
	<linux-nfs@vger.kernel.org>, <linux-cifs@vger.kernel.org>,
	<linux-api@vger.kernel.org>, "'Jeremy Allison'" <jra@samba.org>,
	"'Volker Lendecke'" <Volker.Lendecke@sernet.de>,
	"'Andreas Gruenbacher'" <agruenba@redhat.com>,
	"'Christoph Hellwig'" <hch@infradead.org>
Subject: Re: [PATCH v21 00/22] Richacls
Date: Mon, 23 May 2016 01:20:15 -0000	[thread overview]
Message-ID: <036701d1b491$44b3b2a0$ce1b17e0$@codenest.com> (raw)

> On Tue, May 10, 2016 at 06:18:10AM +0200, Volker Lendecke wrote:
> > On Tue, May 10, 2016 at 12:02:33AM +0200, Andreas Gruenbacher wrote:
> > > What more can I do to finally get this merged?
> > 
> > While I am not the one to comment on kernel specifics, from a pure Samba
> > user space perspective let me say: We need this. NOW.
>
> +1 from me. This is something that many vendors need
> and have needed for a very long time. Getting this
> in will allow *large* amounts of existing storage to
> be migrated to Linux.

As a "mere" end-user of SAMBA, +1 from me also...  It's my understanding
that this patch set would help eliminate the need for hacks like
vfs_acl_xattr that store ACLs in extended attributes that only SAMBA
understands.  If the file system itself can respect the ACLs that seems
like a lot cleaner solution.

James

             reply	other threads:[~2016-05-23  1:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23  1:20 James Johnston [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-05-09 22:02 Andreas Gruenbacher
2016-05-10  4:18 ` Volker Lendecke
2016-05-10  8:11   ` Jeremy Allison
2016-05-10  8:20     ` Volker Lendecke
2016-05-10 15:55     ` Frank Filz

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='036701d1b491$44b3b2a0$ce1b17e0$@codenest.com' \
    --to=johnstonj.public@codenest.com \
    --cc=Volker.Lendecke@sernet.de \
    --cc=agruenba@redhat.com \
    --cc=hch@infradead.org \
    --cc=jra@samba.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --subject='Re: [PATCH v21 00/22] Richacls' \
    /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

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).