From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Frank Filz" Subject: RE: [PATCH v23 08/22] richacl: Compute maximum file masks from an acl Date: Wed, 13 Jul 2016 12:38:50 -0700 Message-ID: <018b01d1dd3e$2f868170$8e938450$@mindspring.com> References: <1467294433-3222-1-git-send-email-agruenba@redhat.com> <1467294433-3222-9-git-send-email-agruenba@redhat.com> <1467728537.3800.32.camel@redhat.com> <014101d1d6df$e059fd20$a10df760$@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Cc: "'Jeff Layton'" , "'Alexander Viro'" , "'Christoph Hellwig'" , "'Theodore Ts'o'" , "'Andreas Dilger'" , "'J. Bruce Fields'" , "'Trond Myklebust'" , "'Anna Schumaker'" , "'Dave Chinner'" , "'linux-ext4'" , "'XFS Developers'" , "'LKML'" , "'linux-fsdevel'" , "'Linux NFS Mailing List'" , , "'Linux API'" To: "'Andreas Gruenbacher'" Return-path: In-Reply-To: Content-Language: en-us Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-cifs.vger.kernel.org > > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay3.corp.sgi.com [198.149.34.15]) by oss.sgi.com (Postfix) with ESMTP id 455417CA6 for ; Wed, 13 Jul 2016 14:40:32 -0500 (CDT) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay3.corp.sgi.com (Postfix) with ESMTP id D1433AC002 for ; Wed, 13 Jul 2016 12:40:28 -0700 (PDT) Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by cuda.sgi.com with ESMTP id vMOoEiHyQ2Jd4FKV (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 13 Jul 2016 12:40:26 -0700 (PDT) From: "Frank Filz" References: <1467294433-3222-1-git-send-email-agruenba@redhat.com> <1467294433-3222-9-git-send-email-agruenba@redhat.com> <1467728537.3800.32.camel@redhat.com> <014101d1d6df$e059fd20$a10df760$@mindspring.com> In-Reply-To: Subject: RE: [PATCH v23 08/22] richacl: Compute maximum file masks from an acl Date: Wed, 13 Jul 2016 12:38:50 -0700 Message-ID: <018b01d1dd3e$2f868170$8e938450$@mindspring.com> MIME-Version: 1.0 Content-Language: en-us List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: 'Andreas Gruenbacher' Cc: "'J. Bruce Fields'" , 'Linux NFS Mailing List' , 'Theodore Ts'o' , 'Jeff Layton' , linux-cifs@vger.kernel.org, 'Linux API' , 'Trond Myklebust' , 'LKML' , 'XFS Developers' , 'Christoph Hellwig' , 'Andreas Dilger' , 'Alexander Viro' , 'linux-fsdevel' , 'linux-ext4' , 'Anna Schumaker' > > 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 _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Frank Filz" Subject: RE: [PATCH v23 08/22] richacl: Compute maximum file masks from an acl Date: Wed, 13 Jul 2016 12:38:50 -0700 Message-ID: <018b01d1dd3e$2f868170$8e938450$@mindspring.com> References: <1467294433-3222-1-git-send-email-agruenba@redhat.com> <1467294433-3222-9-git-send-email-agruenba@redhat.com> <1467728537.3800.32.camel@redhat.com> <014101d1d6df$e059fd20$a10df760$@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: Content-Language: en-us Sender: linux-fsdevel-owner@vger.kernel.org To: 'Andreas Gruenbacher' Cc: 'Jeff Layton' , 'Alexander Viro' , 'Christoph Hellwig' , 'Theodore Ts'o' , 'Andreas Dilger' , "'J. Bruce Fields'" , 'Trond Myklebust' , 'Anna Schumaker' , 'Dave Chinner' , 'linux-ext4' , 'XFS Developers' , 'LKML' , 'linux-fsdevel' , 'Linux NFS Mailing List' , linux-cifs@vger.kernel.org, 'Linux API' List-Id: linux-api@vger.kernel.org > > 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