[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHc6FU64SzTN23LMzGcPex=jRz_Euwb_CHrW=kX+A5sn8=SFSg@mail.gmail.com>
Date: Mon, 14 Mar 2016 14:02:33 +0100
From: Andreas Gruenbacher <agruenba@...hat.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
"J. Bruce Fields" <bfields@...ldses.org>,
Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
"Theodore Ts'o" <tytso@....edu>, linux-cifs@...r.kernel.org,
Linux API <linux-api@...r.kernel.org>,
Trond Myklebust <trond.myklebust@...marydata.com>,
LKML <linux-kernel@...r.kernel.org>,
XFS Developers <xfs@....sgi.com>,
Andreas Dilger <adilger.kernel@...ger.ca>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Jeff Layton <jlayton@...chiereds.net>,
linux-ext4 <linux-ext4@...r.kernel.org>,
Anna Schumaker <anna.schumaker@...app.com>
Subject: Re: [PATCH v18 21/22] ext4: Add richacl support
On Fri, Mar 11, 2016 at 3:27 PM, Christoph Hellwig <hch@...radead.org> wrote:
>> +static inline int
>> +ext4_acl_chmod(struct inode *inode, umode_t mode)
>> +{
>> + if (IS_RICHACL(inode))
>> + return richacl_chmod(inode, inode->i_mode);
>> + return posix_acl_chmod(inode, inode->i_mode);
>> +}
>
> Thi isn't ext4-specific and potentially duplicated in every caller.
> Please provide this as a common helper.
This can go in neither fs.h nor posix_acl.h nor richacl.h unless we
turn it into a macro, and I don't think we want to add a new header
file for such extreme trivia.
> Also while we're at it, the mode argument is ignore and the function
> always uses inode->i_mode instead.
Right, thanks.
Andreas
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists