All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Jan Kara <jack@suse.cz>, ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: enable acls and user_xattr by default
Date: Wed, 23 Feb 2011 12:31:52 -0500	[thread overview]
Message-ID: <20110223173152.GM2924@thunk.org> (raw)
In-Reply-To: <4D629C78.60600@redhat.com>

On Mon, Feb 21, 2011 at 11:10:16AM -0600, Eric Sandeen wrote:
> 
> Well, I did this initially because Ted & Andreas seemed to want it ;)
> 
> I think the idea is, we should move to deprecating and removing the options
> altogether.  Is there any advantage to having them?  And the first step
> to deprecating them might be to change the default.

Yeah, part of the whole goal is to reduce the number of mount options,
since they have really gotten out of control.  Each mount option is
another adds more to the test combinatorics nightmare.

So basically, the question is how much value does the mount option
add?  In fact changing acl's on and off can in fact cause surprises,
since the posix acl's are designed to be safe when going from the
noacl->acl case.  That is, the additional information in the posix
acl's are designed to take away rights, but not add access rights.
But that also means that if you have a file system that had ACL's to
restrict access rights, and then you mount it without using the acl
option, users who aren't supposed to have access to the file might
find themselves with access.

So changing things to have acl's on by default just seems to make
sense....

						- Ted

  reply	other threads:[~2011-02-23 17:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-18 20:31 [PATCH] ext4: enable acls and user_xattr by default Eric Sandeen
2011-02-21 13:46 ` Jan Kara
2011-02-21 17:10   ` Eric Sandeen
2011-02-23 17:31     ` Ted Ts'o [this message]
2011-02-24 11:49       ` Jan Kara
2011-02-24 12:19         ` Theodore Tso
2011-02-24 13:57           ` Jan Kara
2011-02-24 16:49             ` Ted Ts'o
2011-02-24 18:31               ` Jan Kara
2011-02-23 22:51 ` Ted Ts'o

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=20110223173152.GM2924@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.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.