[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <018b01d1dd3e$2f868170$8e938450$@mindspring.com>
Date: Wed, 13 Jul 2016 12:38:50 -0700
From: "Frank Filz" <ffilzlnx@...dspring.com>
To: "'Andreas Gruenbacher'" <agruenba@...hat.com>
Cc: "'Jeff Layton'" <jlayton@...hat.com>,
"'Alexander Viro'" <viro@...iv.linux.org.uk>,
"'Christoph Hellwig'" <hch@...radead.org>,
"'Theodore Ts'o'" <tytso@....edu>,
"'Andreas Dilger'" <adilger.kernel@...ger.ca>,
"'J. Bruce Fields'" <bfields@...ldses.org>,
"'Trond Myklebust'" <trond.myklebust@...marydata.com>,
"'Anna Schumaker'" <anna.schumaker@...app.com>,
"'Dave Chinner'" <david@...morbit.com>,
"'linux-ext4'" <linux-ext4@...r.kernel.org>,
"'XFS Developers'" <xfs@....sgi.com>,
"'LKML'" <linux-kernel@...r.kernel.org>,
"'linux-fsdevel'" <linux-fsdevel@...r.kernel.org>,
"'Linux NFS Mailing List'" <linux-nfs@...r.kernel.org>,
<linux-cifs@...r.kernel.org>,
"'Linux API'" <linux-api@...r.kernel.org>
Subject: RE: [PATCH v23 08/22] richacl: Compute maximum file masks from an acl
> > Hmm, but does that result in examining the whole ACL for most access
> checks, at least for files where most of the accesses are by the owner, or a
> member of a specific group (with perhaps a ton of special case users added
> on the end)?
>
> I don't understand -- what does this algorithm have to do with access checks?
Oh, sorry, misread the patch... got caught up looking at a tree and not seeing the forest...
Frank
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
Powered by blists - more mailing lists