Return-Path: Received: from [198.137.202.9] ([198.137.202.9]:50780 "EHLO bombadil.infradead.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S933405AbcCOHP3 (ORCPT ); Tue, 15 Mar 2016 03:15:29 -0400 Date: Tue, 15 Mar 2016 00:14:39 -0700 From: Christoph Hellwig To: Steve French Cc: Andreas Gruenbacher , Christoph Hellwig , Alexander Viro , "J. Bruce Fields" , Linux NFS Mailing List , "Theodore Ts'o" , "linux-cifs@vger.kernel.org" , Linux API , Trond Myklebust , LKML , XFS Developers , Andreas Dilger , linux-fsdevel , Jeff Layton , linux-ext4 , Anna Schumaker Subject: Re: [PATCH v18 00/22] Richacls (Core and Ext4) Message-ID: <20160315071439.GE19747@infradead.org> References: <1456733847-17982-1-git-send-email-agruenba@redhat.com> <20160311140134.GA14808@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-nfs-owner@vger.kernel.org List-ID: On Fri, Mar 11, 2016 at 02:05:16PM -0600, Steve French wrote: > A loosely related question is what can be done for tools around existing > interfaces for ACLs. I recently found out NTFS-3g has this xattr: > > static const char nf_ns_xattr_ntfs_acl[] = "system.ntfs_acl"; > > which allows you to query system.ntfs_acl xattr to get their full ACL Bah. Filesystems really have no business exposing random system xattrs, and we really need to add a filter to fs/xattr.c to not expose arbitrary attrs ouside the user.* prefix.