public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Filz <ffilzlnx@us.ibm.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: NFS List <linux-nfs@vger.kernel.org>,
	NFS V4 Mailing List <nfsv4@linux-nfs.org>
Subject: Re: [PATHC] nfsd: Fix a couple issues with POSIX->NFSv4 ACL conversion
Date: Thu, 27 Aug 2009 10:40:11 -0700	[thread overview]
Message-ID: <1251394811.32255.6.camel@dyn9047022153> (raw)
In-Reply-To: <20090824235944.GH8532@fieldses.org>

On Mon, 2009-08-24 at 19:59 -0400, J. Bruce Fields wrote:
> On Fri, Aug 14, 2009 at 03:02:30PM -0700, Frank Filz wrote:
> > 1. GROUP@ Allow entry doesn't have NFS4_ACE_IDENTIFIER_GROUP, This
> > appears to have been introduced by accident as part of commit
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=bec50c47aaf6f1f9247f1860547ab394a0802a4c
> 
> It's good to flip that bit every now and then just to keep client
> implementations on their toes....
> 
> 	(Slightly more seriously, the 4.1 draft says "The
> 	ACE4_IDENTIFIER_GROUP flag MUST be ignored on entries with these
> 	special identifiers.  When encoding entries with these special
> 	identifiers, the ACE4_IDENTIFIER_GROUP flag SHOULD be set to
> 	zero."  It really shouldn't matter either way, but the point is
> 	that this flag is used to distinguish named users from named
> 	groups (since unix allows a group to have the same name as a
> 	user), so it doesn't really make sense to use it on a special
> 	identifier such as this.)

Ok, that makes sense, in that case, we probably should have this
fragment to remove the flag from the GROUP@ deny entry:

@@ -321,7 +321,7 @@ _posix_to_nfsv4_one(struct posix_acl *pacl, struct nfs4_acl *acl,
 	deny = ~pas.group & pas.other;
 	if (deny) {
 		ace->type = NFS4_ACE_ACCESS_DENIED_ACE_TYPE;
-		ace->flag = eflag | NFS4_ACE_IDENTIFIER_GROUP;
+		ace->flag = eflag;
 		ace->access_mask = deny_mask_from_posix(deny, flags);
 		ace->whotype = NFS4_ACL_WHO_GROUP;
 		ace++;



  reply	other threads:[~2009-08-27 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 22:02 [PATHC] nfsd: Fix a couple issues with POSIX->NFSv4 ACL conversion Frank Filz
2009-08-24 23:59 ` J. Bruce Fields
2009-08-27 17:40   ` Frank Filz [this message]
2009-08-27 21:37     ` J. Bruce Fields

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=1251394811.32255.6.camel@dyn9047022153 \
    --to=ffilzlnx@us.ibm.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.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