[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110223173152.GM2924@thunk.org>
Date: Wed, 23 Feb 2011 12:31:52 -0500
From: Ted Ts'o <tytso@....edu>
To: Eric Sandeen <sandeen@...hat.com>
Cc: Jan Kara <jack@...e.cz>,
ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] ext4: enable acls and user_xattr by default
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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists