From: "James Johnston" <johnstonj.public-Kk+ApOtKMVJWk0Htik3J/w@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
'Jeremy Allison' <jra-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>,
'Volker Lendecke'
<Volker.Lendecke-3ekOc4rQMZmzQB+pC5nmwQ@public.gmane.org>,
'Andreas Gruenbacher'
<agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
'Christoph Hellwig' <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.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
WARNING: multiple messages have this Message-ID (diff)
From: "James Johnston" <johnstonj.public-Kk+ApOtKMVJWk0Htik3J/w@public.gmane.org>
To: <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"'Jeremy Allison'" <jra-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>,
"'Volker Lendecke'"
<Volker.Lendecke-3ekOc4rQMZmzQB+pC5nmwQ@public.gmane.org>,
"'Andreas Gruenbacher'"
<agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"'Christoph Hellwig'"
<hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.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
WARNING: multiple messages have this Message-ID (diff)
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
next reply other threads:[~2016-05-23 1:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 1:20 James Johnston [this message]
2016-05-23 1:20 ` [PATCH v21 00/22] Richacls James Johnston
2016-05-23 1:20 ` James Johnston
-- strict thread matches above, loose matches on Subject: below --
2016-05-09 22:02 Andreas Gruenbacher
2016-05-09 22:02 ` Andreas Gruenbacher
2016-05-09 22:02 ` Andreas Gruenbacher
2016-05-10 4:18 ` Volker Lendecke
2016-05-10 4:18 ` Volker Lendecke
[not found] ` <20160510041809.GB1079-3ekOc4rQMZmzQB+pC5nmwQ@public.gmane.org>
2016-05-10 8:11 ` Jeremy Allison
2016-05-10 8:11 ` Jeremy Allison
2016-05-10 8:11 ` Jeremy Allison
2016-05-10 8:20 ` Volker Lendecke
2016-05-10 8:20 ` Volker Lendecke
2016-05-10 8:20 ` Volker Lendecke
2016-05-10 8:20 ` Volker Lendecke
2016-05-10 15:55 ` Frank Filz
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-kk+apotkmvjwk0htik3j/w@public.gmane.org \
--cc=Volker.Lendecke-3ekOc4rQMZmzQB+pC5nmwQ@public.gmane.org \
--cc=agruenba-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=jra-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.