From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out01.mta.xmission.com ([166.70.13.231]:53706 "EHLO out01.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751795AbeBZQfv (ORCPT ); Mon, 26 Feb 2018 11:35:51 -0500 From: ebiederm@xmission.com (Eric W. Biederman) To: Miklos Szeredi Cc: lkml , Linux Containers , linux-fsdevel , Alban Crequy , Seth Forshee , Sargun Dhillon , Dongsu Park , "Serge E. Hallyn" References: <878tbmf5vl.fsf@xmission.com> <20180221202908.17258-4-ebiederm@xmission.com> <87inao6dfa.fsf@xmission.com> <87mv004p0t.fsf@xmission.com> Date: Mon, 26 Feb 2018 10:35:17 -0600 In-Reply-To: (Miklos Szeredi's message of "Mon, 26 Feb 2018 08:47:21 +0100") Message-ID: <87zi3v1zga.fsf@xmission.com> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [PATCH v6 4/5] fuse: Ensure posix acls are translated outside of init_user_ns Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Miklos Szeredi writes: > On Thu, Feb 22, 2018 at 11:50 PM, Eric W. Biederman > wrote: > >> So if we could figure out how to use the generic acl support for the old >> brand of fuse filesystems that don't set FUSE_POSIX_ACL it would be much >> easier to support them long term. > > Simplest and most robust way seems to be to do everything the same (as > with FUSE_POSIX_ACL) but tell the vfs not to cache the acl. Good point. That sounds like for the !fc->posix_acl case we just need a careful use of "forget_all_cached_acls(inode)". I will take a quick look at that, and see if that is easy/sufficient to cover the legacy fuse case. Otherwise I will go with what I already have here. That feels like a better path. And internally I would call what is today fc->posix_acl fc->cached_posix_acl. To better convey the intent. Fingers crossed. Eric