All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Prevent mount with "-o acl" if acl isn't	supported.
Date: Thu, 11 Jun 2009 08:43:49 -0700	[thread overview]
Message-ID: <20090611154349.GD11636@ca-server1.us.oracle.com> (raw)
In-Reply-To: <1244667835-16907-1-git-send-email-tao.ma@oracle.com>

On Thu, Jun 11, 2009 at 05:03:55AM +0800, Tao Ma wrote:
> Currently, if we don't enable CONFIG_OCFS2_FS_POSIX_ACL, ocfs2
> will not support acl. That is OK.
> 
> But in the following case:
> 1. kernel isn't built to support acl.
> 2. mount -t ocfs2 -o acl /dev/sdx /mnt/ocfs2.
> It sucesses. And what's more, if I do "mount|grep sdx" will get
> /dev/sdx on /mnt/ocfs2 type ocfs2 (rw,acl,heartbeat=none)
> 
> So a normal user will just think acl now is ok for the volume and
> he will surely be puzzled when he tries setfacl and fails with
> "Operation not supported".
> 
> The good thing is that the kernel already printk some useful
> information, so this patch just tries to prevent the user from
> mounting the volume.

	Hmm, everyone else seems to do it the way we have been.  Trying
to think about the surprise you describe vs the surprise of ocfs2 being
different than other linux filesystms.

Joel

-- 

"Here's something to think about:  How come you never see a headline
 like ``Psychic Wins Lottery''?"
	- Jay Leno

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2009-06-11 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 21:03 [Ocfs2-devel] [PATCH] ocfs2: Prevent mount with "-o acl" if acl isn't supported Tao Ma
2009-06-11 15:43 ` Joel Becker [this message]
2009-06-11 15:58   ` Joel Becker
2009-06-12  1:04     ` Tao Ma

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=20090611154349.GD11636@ca-server1.us.oracle.com \
    --to=joel.becker@oracle.com \
    --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.