All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jiri Horky <jiri.horky@gmail.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 server ignores local filesystem's POSIX ACL
Date: Tue, 12 Feb 2013 10:55:07 -0500	[thread overview]
Message-ID: <20130212155507.GD32745@fieldses.org> (raw)
In-Reply-To: <511A4B90.9010007@gmail.com>

On Tue, Feb 12, 2013 at 03:02:56PM +0100, Jiri Horky wrote:
> Hi,
> On 02/11/2013 10:41 PM, J. Bruce Fields wrote:
> >On Mon, Feb 11, 2013 at 04:01:33PM -0500, J. Bruce Fields wrote:
> >>That shouldn't matter (assuming it's not actually owned by "nobody" on
> >>the server.)
> >Beats me.  The network trace does indeed seem to show a succesful create
> >(and a preceding access op that allows access that I would have expected
> >to fail).
> >
> >I don't see how that could have happened--the server doesn't actually
> >enforce the ACL itself, it depends on common vfs code for that, so
> >there's probably something obvious we're overlooking.  You're positive
> >the file's being created in the same directory that you set that acl on?
> >
> >--b.
> we tracked the cause down to the "enhanced xfs" module from SGI
> (sgi-enhancedxfs-kmp-default-2.5_2.6.32.12_0.7-sgi250rp13.sles11).
> With a standard xfs module
> (sgi-xfs-kmp-default-6.5.0.14_2.6.32.12_0.7-sgi12111921) or on a
> ext3 file systems, the server respects ACL correctly. Seems like the
> enhancement went into wrong direction :) Lets file a bug against the
> vendor.

OK, thanks for the followup.  That's extremely weird.

--b.

      reply	other threads:[~2013-02-12 15:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 15:29 NFSv4 server ignores local filesystem's POSIX ACL Jiri Horky
2013-02-11 18:22 ` J. Bruce Fields
2013-02-11 18:32   ` Myklebust, Trond
2013-02-11 18:49     ` J. Bruce Fields
2013-02-11 20:40       ` Jiri Horky
2013-02-11 21:01         ` J. Bruce Fields
2013-02-11 21:41           ` J. Bruce Fields
2013-02-12 14:02             ` Jiri Horky
2013-02-12 15:55               ` J. Bruce Fields [this message]

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=20130212155507.GD32745@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=jiri.horky@gmail.com \
    --cc=linux-nfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.