[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160321160922.GA18734@infradead.org>
Date: Mon, 21 Mar 2016 09:09:22 -0700
From: Christoph Hellwig <hch@...radead.org>
To: "J. Bruce Fields" <bfields@...ldses.org>
Cc: Christoph Hellwig <hch@...radead.org>,
Andreas Gruenbacher <agruenba@...hat.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-nfs@...r.kernel.org, Theodore Ts'o <tytso@....edu>,
linux-cifs@...r.kernel.org, linux-api@...r.kernel.org,
Trond Myklebust <trond.myklebust@...marydata.com>,
linux-kernel@...r.kernel.org, xfs@....sgi.com,
Andreas Dilger <adilger.kernel@...ger.ca>,
linux-fsdevel@...r.kernel.org,
Jeff Layton <jlayton@...chiereds.net>,
linux-ext4@...r.kernel.org,
Anna Schumaker <anna.schumaker@...app.com>
Subject: Re: [PATCH v18 19/22] richacl: Add richacl xattr handler
On Tue, Mar 15, 2016 at 05:05:26PM -0400, J. Bruce Fields wrote:
> > That people get confused between the attr used by the xattr syscall
> > interface and the attr used to store things on disk or the protocol.
> > This has happened every time we have non-native support, e.g. XFS, NFS,
> > CIFS, ntfs, etc. And it's only going to become worse.
>
> How has that confusion caused problems in practice?
We had all kinds of bugs in this area that were only slowly uncovered.
We also had all kind of privilegue escalations with (non-ACLs) xattrs
as people never grasped the way different free-form namespaces have
different permission checking.
Powered by blists - more mailing lists