From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Muntz, Daniel" <Dan.Muntz@netapp.com>
Cc: linux-nfs@vger.kernel.org, "Myklebust,
Trond" <Trond.Myklebust@netapp.com>,
nfsv4@linux-nfs.org, ffilzlnx@linux.vnet.ibm.com,
Steve French <smfrench@gmail.com>,
jra@samba.org, agruen@suse.de
Subject: Re: POSIX ACL support for NFSV4 (using sideband protocol)
Date: Thu, 3 Sep 2009 16:11:46 +0530 [thread overview]
Message-ID: <20090903104146.GA11784@skywalker.linux.vnet.ibm.com> (raw)
In-Reply-To: <7A24DF798E223B4C9864E8F92E8C93EC03F0ABED@SACMVEXC1-PRD.hq.netapp.com>
On Thu, Sep 03, 2009 at 12:46:09AM -0700, Muntz, Daniel wrote:
> I've always thought of NFS as a means for making physical file systems
> available across a network. NFS having its own ACLs doesn't fit this
> model. E.g., "NFS ACLs" will never be integrated into NTFS. However, I
> could imagine NFS ACLs solving the general problem if they were to form
> a superset of the ACLs of exportable physical file systems, and the
> mechanism for interpreting ACLs for a particular physical file system
> could be encoded (or modularized) in such a way that NFS' evaluation of
> ACL operations has the same results as the physical file system's
> execution of the same ACL operations. You could have a POSIX ACL
> module, NTFS ACL module, etc. There's a challenge for 4.2.
>
> ACLs could possibly be made completely opaque to NFS with a module-based
> approach.
>
What would be the acl model on the client side ? Considering that POSIX ACL
is looked at as the native acl model in Linux, I guess we should have the ability
to modify the ACLs using POSIX ACL tools on the nfs client
-aneesh
_______________________________________________
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 10:41 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 [this message]
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
-- 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=20090903104146.GA11784@skywalker.linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=Dan.Muntz@netapp.com \
--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 \
/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