Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp511440ybv; Wed, 19 Feb 2020 04:06:51 -0800 (PST) X-Google-Smtp-Source: APXvYqyhXGfE+IRvg4DGdp0cWedR41+92Y3ZhC+ZTT48ja0OwdbPXCkruT4tDZYXhmk/ruKHzY5k X-Received: by 2002:a9d:bb8:: with SMTP id 53mr17538230oth.150.1582114011054; Wed, 19 Feb 2020 04:06:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582114011; cv=none; d=google.com; s=arc-20160816; b=PaRHfn/HY9djtD6mzwt005NdjI+8E2oH0OJM8H+TvpQzYBcwAO51Cks6YhOTOrtSNs jkENyPf/ubcl5YwgFRTg+Yr56zzeuTZAwu3d1eHoRTGExqWBVtJJdC1eS+BH4kIUM8yM FBmMz0C/DFBm9vu+bxSXluQqboOeg+v6BPp9YvWRoRznbWcuTVCahvYdewta63t8+zFV zFJOFN+6welRoYrJwb6Z/p1pjCdIrC0XJit2kMyyxYp3eKAkso+RlBB/apib1FF6iCix vvDqwKWfbrzjqe3Jdx9ZZcnd9VwWWQXlUCcZPQIUV4HHwPBDxHpEj08rZXWzj90yo5/i N1zA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=I8GwdSlLPwZNmJu6X0lB1LKupxGJpN6NR57OI/I/w5Q=; b=YrsZfQP9yMLhrWxQDLzPaBOtdWf7tG3TB2VSQz6v8/B9RmDHba83nHIhrcwEvRWJk0 vHk/n9Tbx20XdcFnA5olwvhQtB76qzn+AeuYhFhlZDigpMH868ODdlwIix/pBZEjcfUE GugszR/ZwuCLeNqxvce+Yv21645kTvO+JbYJCFN5253QocH6wx9IsZKel6Uy0zql93UL Z16nKL+6nk4iUw1AZSKwZysiFQUONMgyenqe4rWqu38FFchWqGoMsOpCpOIxRuz2OMS0 bBaz2S5ARzmmqOGr4twL5EEnsGj+D89HLhWJ1WWwFa0wPwc8XNYZLzWF5ixqbuPM+Pf2 dAZw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f16si9954656oib.269.2020.02.19.04.06.28; Wed, 19 Feb 2020 04:06:51 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726840AbgBSMGY (ORCPT + 99 others); Wed, 19 Feb 2020 07:06:24 -0500 Received: from youngberry.canonical.com ([91.189.89.112]:57574 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726495AbgBSMGY (ORCPT ); Wed, 19 Feb 2020 07:06:24 -0500 Received: from ip5f5bf7ec.dynamic.kabel-deutschland.de ([95.91.247.236] helo=wittgenstein) by youngberry.canonical.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1j4O7B-0002If-8k; Wed, 19 Feb 2020 12:06:05 +0000 Date: Wed, 19 Feb 2020 13:06:04 +0100 From: Christian Brauner To: "Serge E. Hallyn" Cc: =?utf-8?B?U3TDqXBoYW5l?= Graber , "Eric W. Biederman" , Aleksa Sarai , Jann Horn , smbarber@chromium.org, Seth Forshee , Alexander Viro , Alexey Dobriyan , James Morris , Kees Cook , Jonathan Corbet , Phil Estes , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, containers@lists.linux-foundation.org, linux-security-module@vger.kernel.org, linux-api@vger.kernel.org Subject: Re: [PATCH v3 09/25] fs: add is_userns_visible() helper Message-ID: <20200219120604.vqudwaeppebvisco@wittgenstein> References: <20200218143411.2389182-1-christian.brauner@ubuntu.com> <20200218143411.2389182-10-christian.brauner@ubuntu.com> <20200219024233.GA19334@mail.hallyn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200219024233.GA19334@mail.hallyn.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 18, 2020 at 08:42:33PM -0600, Serge Hallyn wrote: > On Tue, Feb 18, 2020 at 03:33:55PM +0100, Christian Brauner wrote: > > Introduce a helper which makes it possible to detect fileystems whose > > superblock is visible in multiple user namespace. This currently only > > means proc and sys. Such filesystems usually have special semantics so their > > behavior will not be changed with the introduction of fsid mappings. > > Hi, > > I'm afraid I've got a bit of a hangup about the terminology here. I > *think* what you mean is that SB_I_USERNS_VISIBLE is an fs whose uids are > always translated per the id mappings, not fsid mappings. But when I see Correct! > the name it seems to imply that !SB_I_USERNS_VISIBLE filesystems can't > be seen by other namespaces at all. > > Am I right in my first interpretation? If so, can we talk about the > naming? Yep, your first interpretation is right. What about: wants_idmaps()