From: Andreas Gruenbacher <agruen@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, trond.myklebust@netapp.com,
nfsv4@linux-nfs.org, sfrench@us.ibm.com
Subject: Re: POSIX ACL support for NFSV4 (using sideband protocol)
Date: Thu, 3 Sep 2009 21:09:52 +0200 [thread overview]
Message-ID: <200909032109.52615.agruen@suse.de> (raw)
In-Reply-To: <20090902164243.GA17126@fieldses.org>
On Wednesday, 2 September 2009 18:42:43 J. Bruce Fields wrote:
> On Wed, Sep 02, 2009 at 05:54:20PM +0530, Aneesh Kumar K.V wrote:
> > This patch series implement POSIX ACL support for NFSV4 clients
> > using sideband protocol.
>
> What motivates this? Who exactly wants this and why? What would be
> the advantages compared to other options, such as:
>
> - native v4 support in filesystems, or
> - improved client-side acl tools that provided a user interface
> for v4 acls closer to that for v3 acls, or
> - a v4.x extension to add support to the main protocol?
I can't speak for Aneesh, but my expectation is that we'll get native NFSv4
ACL support eventually, just maybe not in the next few years. Even then,
systems with native POSIX ACLs will coexist with machines with native NFSv4
ACLs for a long time, and so NFSv4's lack of decent support for POSIX ACLs is
a major problem.
I'm not sure what you mean by improved client-side tool. Some information is
unrecoverably lost when POSIX ACLs are converted into NFSv4 ACLs; no tool on
the client can make up for this. Besides, presenting server-side POSIX ACLs
as similar (but not quite identical) NFSv4 ACLs on the client is really not a
good idea: right now, clients can only guess which NFSv4 ACLs are actually
POSIX ACLs in disguise.
> Is there interest in implementing this on any OS other than linux, or
> would this be a linux-only extension for the forseeable future?
Good question. I would sure prefer a standard solution to a Linux specific
hack -- but that being said, I would prefer a solution to the current
mess ;-)
Thanks,
Andreas
_______________________________________________
NFSv4 mailing list
NFSv4@linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4
next prev parent reply other threads:[~2009-09-03 19:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 12:24 POSIX ACL support for NFSV4 (using sideband protocol) Aneesh Kumar K.V
2009-09-02 12:24 ` [RFC PATCH 1/8] nfs4: Posix acl server side side-band protocol support Aneesh Kumar K.V
2009-09-02 12:24 ` [RFC PATCH 2/8] nfsv4: Switch to generic xattr handling code Aneesh Kumar K.V
2009-09-02 12:24 ` [RFC PATCH 3/8] nfsv4: Add support for posix ACL Aneesh Kumar K.V
2009-09-02 12:24 ` [RFC PATCH 4/8] nfs: use different capability flag for v4 and posix acl Aneesh Kumar K.V
2009-09-02 12:24 ` [RFC PATCH 5/8] nfsv4: Add nfsv4 rpc client side support Aneesh Kumar K.V
2009-09-02 12:24 ` [RFC PATCH 6/8] nfsv4: Implement posix listxattr Aneesh Kumar K.V
2009-09-02 12:24 ` [RFC PATCH 7/8] nfsv4: Implement getfacl Aneesh Kumar K.V
2009-09-02 12:24 ` [RFC PATCH 8/8] nfsv4: Implement setfacl Aneesh Kumar K.V
2009-09-02 16:42 ` POSIX ACL support for NFSV4 (using sideband protocol) 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-02 18:56 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
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
2009-09-02 19:06 Steve French
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=200909032109.52615.agruen@suse.de \
--to=agruen@suse.de \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=sfrench@us.ibm.com \
--cc=trond.myklebust@netapp.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