[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87k4ub9g12.fsf_-_@openvz.org>
Date: Thu, 18 Feb 2010 10:09:13 +0300
From: Dmitry Monakhov <dmonakhov@...nvz.org>
To: Andreas Dilger <adilger@....com>
Cc: "Theodore Ts'o" <tytso@....edu>, linux-fsdevel@...r.kernel.org,
linux-ext4@...r.kernel.org
Subject: [PATCH 08/19] ext4: replace inode uid,gid,mode init with helper v2
Andreas Dilger <adilger@....com> writes:
> On 2010-02-17, at 11:40, Dmitry Monakhov wrote:
>> @@ -985,16 +985,12 @@ got:
>> atomic_dec(&sbi->s_flex_groups[flex_group].free_inodes);
>> }
>>
>> + if (test_opt (sb, GRPID)) {
>
> (style) please don't add the space after "test_opt" back into the code.
Ok, updated, new version attached.
>
>
>> + inode->i_mode = mode;
>> + inode->i_uid = current_fsuid();
>> inode->i_gid = dir->i_gid;
>> } else
>> + inode_init_owner(inode, dir, mode);
>
>
> This code is a bit misleading, since it implies that "i_uid" and
> "i_mode" are set this way due to the GRPID option, even though with
> further investigation it is just set the same way in both cases.
>
> Ted,
> what do you think of just removing the "GRPID" mount option? I
> believe this was around for ages, due to the lack of BSD setgid-on-
> parent functionality in Linux. I don't think it is needed anymore,
> since the BSD functionality is much more flexible (it can be set on a
> per-directory basis instead of for the whole filesystem).
>
> I suppose one way to find out positively would be to add a printk() to
> case Opt_grpid: in the option parsing that this option is deprecated,
> and to contact linux-ext4@...r.kernel.org if you are still using it.
Let's post this as separate patch because this change existing behavior.
>
> Cheers, Andreas
> --
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.
View attachment "0008-ext4-replace-inode-uid-gid-mode-init-with-helper-v2.patch" of type "text/plain" (1136 bytes)
Powered by blists - more mailing lists