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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 6 Oct 2015 02:49:35 -0700
From:	Christoph Hellwig <>
To:	Austin S Hemmelgarn <>
Cc:	Andreas Gruenbacher <>,
	Christoph Hellwig <>,
	Alexander Viro <>,
	Theodore Ts'o <>,
	Andreas Dilger <>,
	"J. Bruce Fields" <>,
	Jeff Layton <>,
	Trond Myklebust <>,
	Anna Schumaker <>,, LKML <>,
	linux-fsdevel <>,,
Subject: Re: [PATCH v8 00/41] Richacls

On Mon, Oct 05, 2015 at 02:58:36PM -0400, Austin S Hemmelgarn wrote:
> I think the point is that a new VFS feature that is easy to integrate in
> multiple filesystems should have support for those filesystems.  A decade
> ago, just having ext* support would probably have been fine, but these days,
> XFS, BTRFS, and F2FS are used just as much (if not more) on production
> systems as ext4, and having support for them right from the start would
> significantly help with adoption of richacls.

That's one reason.  The other is that actually wiring it up for more
than a single consumer shows its actually reasonable generic.  I don't
want to end up with a situration like Posix ACLs again where different
file systems using different on disk formats again.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists