From mboxrd@z Thu Jan 1 00:00:00 1970 From: Miklos Szeredi Subject: Re: [PATCH v8 1/6] fs/posix_acl: Update the comments and support lightweight cache skipping Date: Mon, 5 Mar 2018 10:53:41 +0100 Message-ID: References: <87r2p287i8.fsf_-_@xmission.com> <20180302215919.27207-1-ebiederm@xmission.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20180302215919.27207-1-ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: "Eric W. Biederman" Cc: Linux Containers , lkml , Seth Forshee , Alban Crequy , Sargun Dhillon , linux-fsdevel , Linus Torvalds List-Id: containers.vger.kernel.org On Fri, Mar 2, 2018 at 10:59 PM, Eric W. Biederman wrote: > The code has been missing a way for a ->get_acl method to not cache > a return value without risking invalidating a cached value > that was set while get_acl() was returning. > > Add that support by implementing to_uncachable_acl, to_cachable_acl, > is_uncacheable_acl, and dealing with uncachable acls in get_acl(). I don't like the pointer magic here. Can't the uncachable bit just be added to struct posix_acl? AFAICS that can be done even without increasing the size of that struct (e.g. by unioning it with the rcu_head). Thanks, Miklos