Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1361958 > unrolled thread
| Started by | Christoph Hellwig <hch@infradead.org> |
|---|---|
| First post | 2016-03-21 17:10 +0100 |
| Last post | 2016-03-21 17:10 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v18 19/22] richacl: Add richacl xattr handler Christoph Hellwig <hch@infradead.org> - 2016-03-21 17:10 +0100
| From | Christoph Hellwig <hch@infradead.org> |
|---|---|
| Date | 2016-03-21 17:10 +0100 |
| Subject | Re: [PATCH v18 19/22] richacl: Add richacl xattr handler |
| Message-ID | <rfaz0-86k-5@gated-at.bofh.it> |
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.
Back to top | Article view | linux.kernel
csiph-web