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>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 25 Apr 2012 15:10:33 -0500
From:	Rob Landley <>
To:	Ludwig Nussel <>
	"Jan Kara (maintainer:EXT2 FILE SYSTEM)" <>,
	"Andrew Morton (maintainer:EXT3 FILE SYSTEM)" 
	"Andreas Dilger (maintainer:EXT3 FILE SYSTEM)" 
	"\"Theodore Ts'o\" (maintainer:EXT4 FILE SYSTEM)" <>,,
Subject: Re: [PATCH] implement uid and gid mount options for ext2, ext3 and

On 04/25/2012 06:54 AM, Ludwig Nussel wrote:
> 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 <>
>> 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.

The right thing to do is often more work.  If it allows us to remove
existing duplicate code, even better...

GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code.
Either it's "mere aggregation", or a license violation.  Pick one.
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists