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
| ||
|
Message-ID: <20151007075053.GA8660@infradead.org> Date: Wed, 7 Oct 2015 00:50:54 -0700 From: Christoph Hellwig <hch@...radead.org> To: Andreas Dilger <adilger@...ger.ca> Cc: Andreas Gruenbacher <agruenba@...hat.com>, Christoph Hellwig <hch@...radead.org>, Austin S Hemmelgarn <ahferroin7@...il.com>, Alexander Viro <viro@...iv.linux.org.uk>, Theodore Ts'o <tytso@....edu>, "J. Bruce Fields" <bfields@...ldses.org>, Jeff Layton <jlayton@...chiereds.net>, Trond Myklebust <trond.myklebust@...marydata.com>, Anna Schumaker <anna.schumaker@...app.com>, linux-ext4 <linux-ext4@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-nfs@...r.kernel.org, Linux API <linux-api@...r.kernel.org> Subject: Re: [PATCH v8 00/41] Richacls On Tue, Oct 06, 2015 at 02:26:09PM -0600, Andreas Dilger wrote: > And any disk filesystems that have their own non-POSIX ACLs, such as HFS, NTFS, ZFS would presumably also need to map the in-kernel Richacl format to their on-disk format. No, we did this mistake with Posix ACLs, and we're not going to repeat it here. Filesystems with their own slightly different ACLs must not reuse the interface. -- 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/
Powered by blists - more mailing lists