From: Ludwig Nussel <ludwig.nussel@suse.de>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org,
"Jan Kara (maintainer:EXT2 FILE SYSTEM)" <jack@suse.cz>,
"Andrew Morton (maintainer:EXT3 FILE SYSTEM)"
<akpm@linux-foundation.org>,
"Andreas Dilger (maintainer:EXT3 FILE SYSTEM)"
<adilger.kernel@dilger.ca>,
"\"Theodore Ts'o\" (maintainer:EXT4 FILE SYSTEM)" <tytso@mit.edu>,
linux-ext4@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] implement uid and gid mount options for ext2, ext3 and ext4
Date: Wed, 25 Apr 2012 13:54:26 +0200 [thread overview]
Message-ID: <4F97E5F2.50501@suse.de> (raw)
In-Reply-To: <4F971936.6070809@landley.net>
Rob Landley wrote:
> On 04/24/2012 10:29 AM, Ludwig Nussel wrote:
>> Further development of a patch I sent years ago. I didn't find the
>> time to address the concerns raised back then and forgot about the
>> patch. Now here it is again.
>
> The doc bits look fine:
>
> Acked-by: Rob Landley <rob@landley.net>
>
> As for the design: why isn't this in the VFS instead of in ext234? It
> seems like VFAT is more likely to need this, and I vaguely recall virtfs
> (I.E. 9pfs) doing something similar...?
Yes, file systems like FAT that do not store ownership information
themselves have a uid option. I agree that handling that in vfs itself
would be the more generic solution. It would require more work though.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2012-04-25 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 15:29 [PATCH] implement uid and gid mount options for ext2, ext3 and ext4 Ludwig Nussel
[not found] ` <4F971936.6070809@landley.net>
2012-04-25 11:54 ` Ludwig Nussel [this message]
2012-04-25 20:10 ` Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2012-05-03 9:10 Ludwig Nussel
[not found] ` <4FA2B0C1.4030206@landley.net>
2012-05-03 17: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=4F97E5F2.50501@suse.de \
--to=ludwig.nussel@suse.de \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=tytso@mit.edu \
/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.