Return-Path: Received: from mail-wm0-f42.google.com ([74.125.82.42]:33804 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751373AbcBUVBc (ORCPT ); Sun, 21 Feb 2016 16:01:32 -0500 Subject: Re: richacl(7) man page review comments To: Andreas Gruenbacher References: <56B770B6.7040803@gmail.com> <56B77262.7090107@gmail.com> <56C0F23C.7030902@gmail.com> Cc: mtk.manpages@gmail.com, "J. Bruce Fields" , linux-ext4 , XFS Developers , lkml , linux-fsdevel , Linux NFS Mailing List , linux-cifs@vger.kernel.org, Linux API , Dave Chinner , Christoph Hellwig , Anna Schumaker , Trond Myklebust , Jeff Layton , Andreas Dilger From: "Michael Kerrisk (man-pages)" Message-ID: <56CA25A5.2030100@gmail.com> Date: Sun, 21 Feb 2016 22:01:25 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Sender: linux-nfs-owner@vger.kernel.org List-ID: On 02/20/2016 05:37 PM, Andreas Gruenbacher wrote: > Hi Michael, > > thanks again for all the feedback. I've followed all your suggestions; > again, please see the github repo for the latest version: > > https://github.com/andreas-gruenbacher/richacl > > On Sun, Feb 14, 2016 at 10:31 PM, Michael Kerrisk (man-pages) > wrote: >> Hi Andreas, >> >> Here's a few more comments on the current richacl(7) page >> that I fetched from the git repo. >> [...] >>> .HP >>> .BR dir_inherit "\ (" d ): >>> The entry is inheritable for directories. >> >> "When this flag appears in the ACL entry of a directory, then that entry is >> inherited by new subdirectories created in the directory." >> >> Is that text that I propose correct? > > It's not entirely wrong, but only a small part of the truth. Entries > are inherited such that the permissions in file_inherit entries become > effective for access checking for new files, and the permissions in > dir_inherit entries become effective for access checking for new > directories, recursively. > > Your feedback prompted me to look into the inheritance flag > computation more closely once again, and I found bugs. The steps of > the algorithm are explained in the section "Permissions at > file-creation time", by the way. Hmmm... writing and refining documentation helps find code bugs. Who knew? :-) Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/