public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Valousek <webserv@s3group.cz>
To: Steve French <smfrench@gmail.com>
Cc: ffilzlnx@linux.vnet.ibm.com, linux-nfs@vger.kernel.org,
	nfsv4@linux-nfs.org, Trond Myklebust <Trond.Myklebust@netapp.com>,
	jra@samba.org, agruen@suse.de
Subject: Re: POSIX ACL support for NFSV4 (using sideband protocol)
Date: Thu, 03 Sep 2009 08:20:23 +0200	[thread overview]
Message-ID: <4A9F6027.9050807@s3group.cz> (raw)
In-Reply-To: <524f69650909021353o1e055cbema16495c57cb9909b@mail.gmail.com>


> 2) If POSIX->NFSv4 client mapping is done (as had been suggested IIRC
> by others in the past) at least you lose less data (NFSv4 ACLs are "richer"
> in function than POSIX ACLs - so at least with the POSIX->NFSv4->POSIX
> case you are limiting the user to the subset of choices which are actually
> going to be able to be stored, no inheritence etc.)
>
>   

I must say that I do not understand the motivation either. POSIX is not 
even a standard and should be replaced with NFSv4 acls.
Even now ext3/ext4 support NFSv4 acls (ok. patch is needed but the patch 
is there already).

If the decision was up to me, I would forbid any nfsv4 acls if the 
server can not store them properly (i.e. without any conversion) + 
forbid using nfsv4 with posix acls over sideband protocol (no standard, 
so netapp will never support this and the same is to be expected from 
Windows and Solaris). This is just adding mess and confusion.

My 5 cents...
Ondrej
_______________________________________________
NFSv4 mailing list
NFSv4@linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4

  reply	other threads:[~2009-09-03  6:20 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 [this message]
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
  -- 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=4A9F6027.9050807@s3group.cz \
    --to=webserv@s3group.cz \
    --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