From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve French <smfrench@gmail.com>
Cc: Ondrej Valousek <webserv-K2D8ygZuxnnrBKCeMvbIDA@public.gmane.org>,
linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org,
Trond Myklebust <Trond.Myklebust@netapp.com>,
ffilzlnx@linux.vnet.ibm.com, jra@samba.org, agruen@suse.de
Subject: Re: POSIX ACL support for NFSV4 (using sideband protocol)
Date: Thu, 3 Sep 2009 12:08:45 -0400 [thread overview]
Message-ID: <20090903160845.GF8270@fieldses.org> (raw)
In-Reply-To: <524f69650909030835s41e78436p4b67594cf91de639-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, Sep 03, 2009 at 10:35:35AM -0500, Steve French wrote:
> On Thu, Sep 3, 2009 at 8:55 AM, J. Bruce Fields<bfields@fieldses.org> wrote:
> > On Thu, Sep 03, 2009 at 08:54:06AM -0500, Steve French wrote:
> >> if someone were able to convince the linux-fsdevel community to change
> >> fs/posix_acls.c
> >> (or add an fs/cifs_acls.c) to handle NFSv4/CIFS/NTFS ACL evaluation, and add
> >> support to store these richer ACLs on disk for the future (e.g. for
> >> btrfs), that would be
> >> great - but with no local file system in kernel which can store NFSv4 ACLs and
> >> no code to evaluate these ACLs in the VFS and with a NACK from fsdevel when
> >
> > I don't remember that--do you have a pointer?
>
> Aneesh mentioned one strongly worded objection (I remember more resistance
> from others too)
>
> http://kerneltrap.org/mailarchive/linux-fsdevel/2006/6/24/313526
Yes, Christoph's always been vehemently opposed. I share his distaste
for NFSv4/NT ACLs, but I agree with Trond that a solid implementation
with a demonstrated need from CIFS, NFSv4, NTFS, etc., would be likely
to overcome such objections.
--b.
next prev parent reply other threads:[~2009-09-03 16:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 18:56 POSIX ACL support for NFSV4 (using sideband protocol) Steve French
2009-09-02 20:22 ` J. Bruce Fields
2009-09-02 20:53 ` Steve French
2009-09-03 6:20 ` Ondrej Valousek
2009-09-03 7:46 ` Muntz, Daniel
2009-09-03 10:41 ` Aneesh Kumar K.V
2009-09-03 13:36 ` Steve French
2009-09-03 13:54 ` J. Bruce Fields
2009-09-03 13:57 ` Steve French
2009-09-03 15:01 ` David P. Quigley
2009-09-03 13:54 ` Steve French
2009-09-03 13:55 ` J. Bruce Fields
2009-09-03 15:35 ` Steve French
[not found] ` <524f69650909030835s41e78436p4b67594cf91de639-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-03 16:08 ` J. Bruce Fields [this message]
2009-09-03 14:09 ` Trond Myklebust
2009-09-03 18:55 ` Andreas Gruenbacher
2009-09-03 14:16 ` J. Bruce Fields
2009-09-03 15:14 ` Steve French
2009-10-05 16:31 ` Andreas Gruenbacher
2009-10-05 16:44 ` Steve French
2009-10-05 17:09 ` Andreas Gruenbacher
2009-10-05 17:19 ` Steve French
-- strict thread matches above, loose matches on Subject: below --
2009-09-02 19:06 Steve French
2009-09-02 12:24 Aneesh Kumar K.V
2009-09-02 16:42 ` J. Bruce Fields
2009-09-02 17:49 ` Aneesh Kumar K.V
2009-09-02 18:27 ` J. Bruce Fields
2009-09-03 19:09 ` Andreas Gruenbacher
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=20090903160845.GF8270@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=agruen@suse.de \
--cc=ffilzlnx@linux.vnet.ibm.com \
--cc=jra@samba.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=smfrench@gmail.com \
--cc=webserv-K2D8ygZuxnnrBKCeMvbIDA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox