All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] [RFC] Mount option trap for users
Date: Wed, 14 Oct 2009 02:27:52 +0200	[thread overview]
Message-ID: <20091014002752.GA19960@lst.de> (raw)
In-Reply-To: <20091013194615.GA23257@mail.oracle.com>

On Tue, Oct 13, 2009 at 12:46:16PM -0700, Joel Becker wrote:
> 	Actually, I just realized where we really differ from the other
> filesystems.  We're clustered, but CONFIG_OCFS2_POSIX_ACL isn't a
> feature flag.  We can, in theory, have two nodes.  Both have xattrs
> enabled, but only one has acls compiled into the kernel.  Now we're
> fucked.
> 	As far as I can tell, there is no way for the non-acl driver to
> notice that other nodes are using acls and reject the mount.  Thoughts?

So why do you allow compiling ocfs2 without ACLs at all?

  parent reply	other threads:[~2009-10-14  0:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 14:56 [Ocfs2-devel] [PATCH] [RFC] Mount option trap for users Jan Kara
2009-09-14 19:44 ` Joel Becker
2009-09-15  9:24   ` Jan Kara
2009-09-17 23:00     ` Mark Fasheh
2009-10-06 17:17       ` Jan Kara
2009-10-13 19:46         ` Joel Becker
2009-10-13 20:12           ` Jan Kara
2009-10-13 20:43             ` Joel Becker
2009-10-13 22:30               ` Jan Kara
2009-10-13 22:50                 ` Mark Fasheh
2009-10-13 23:02                   ` Joel Becker
2009-10-13 23:50                     ` Mark Fasheh
2009-10-14  0:31                       ` Joel Becker
2009-10-14  0:27           ` Christoph Hellwig [this message]
2009-10-14  0:38             ` Joel Becker
2009-10-14  9:41               ` Jan Kara
2009-10-14 10:03                 ` Joel Becker
2009-10-14 10:09                   ` Jan Kara
2009-10-14 16:27                   ` Mark Fasheh
2009-10-14 18:11                     ` Jan Kara
2009-10-14 20:03                       ` Joel Becker

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=20091014002752.GA19960@lst.de \
    --to=hch@lst.de \
    --cc=ocfs2-devel@oss.oracle.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 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.