linux-kernel - Re: [PATCH] implement uid and gid mount options for ext2, ext3 and ext4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 3 May 2012 13:51:44 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Rob Landley <rob@...dley.net>
Cc:	Ludwig Nussel <ludwig.nussel@...e.de>,
	linux-kernel@...r.kernel.org,
	"Jan Kara (maintainer:EXT2 FILE SYSTEM)" <jack@...e.cz>,
	"Andrew Morton (maintainer:EXT3 FILE SYSTEM)" 
	<akpm@...ux-foundation.org>,
	"Andreas Dilger (maintainer:EXT3 FILE SYSTEM)" 
	<adilger.kernel@...ger.ca>,
	"open list:EXT2 FILE SYSTEM" <linux-ext4@...r.kernel.org>,
	"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH] implement uid and gid mount options for ext2, ext3 and
 ext4

On Thu, May 03, 2012 at 11:22:25AM -0500, Rob Landley wrote:
> > When using 'real' file systems on removable storage devices such as
> > hard disks or usb sticks people quickly face the problem that their
> > Linux users have different uids on different machines.
> 
> I still think this belongs at the VFS level, not in individual filesystems.

I agree with Rob; as much as possible, this should be done at the VFS
level.  The problem is that there will need to be at least some
support in the individual file system, since there isn't a good place
for the VFS to intercept the internal file system iget() function to
patch in the override uid/gid values.

So the question at this point is whether it's cleaner to have the
functionality split between the VFS and the file system layers (i.e.,
with the options parsing and storing the override uid/gid values in
the super_block structure) or keeping it all in the file system layer,
and accepting the duplication of code across multiple file systems.

My preference leans towards the former (pushing as much as we can into
the VFS layer), but I can see the other point of view.

Regards,

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/