From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EA36CC433DF for ; Sun, 17 May 2020 15:00:56 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A619C2070A for ; Sun, 17 May 2020 15:00:56 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=rath.org header.i=@rath.org header.b="mMgblVV6"; dkim=pass (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="3erz6sa5" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728007AbgEQPA4 (ORCPT ); Sun, 17 May 2020 11:00:56 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:60701 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727970AbgEQPAz (ORCPT ); Sun, 17 May 2020 11:00:55 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7B2C95C0091 for ; Sun, 17 May 2020 11:00:54 -0400 (EDT) Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Sun, 17 May 2020 11:00:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rath.org; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm2; bh=PYQdK a4yEw9ZT/evyfWGU9X9I4J6+RvfX5WenXXhhzw=; b=mMgblVV6pJjqRv2PQ093z WMKULfoywwpwvqKwNDK1wh+I+gu79t5P7F3G7wprdhlob58gAvtdXvFswiWl9GTH oEcSup6YbzvZwMJ8s6YogwJ9TQmVKzTWCdtKfyNO0z43ORux95pwjF/8iihXlFiC oxA9CBPZuEuGMA3u9eYG8uLZ4UgZIy0vOOpHkuDjt4e0eFozoF+YNzviAU/Q9XuL yA4wS0ei/nHE+NHcZI00OIaeJo/eBJGYA+aBYM3KoFHsr/7CoCVipIwRqqBB1man Os+sZ855w7qnWddaJKsvjwxnPgncDoikgzCLHO+iG08RHwmxi63c3SqESdL817PJ w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=PYQdKa4yEw9ZT/evyfWGU9X9I4J6+RvfX5WenXXhh zw=; b=3erz6sa5/gtyOODTcltCRciXq4W9IbCxCSK+ZvVDoKEPx4HCj3tkaeAqD 5KLTJ62zZqfvgmoMJ9tstCIvwgrIiKtH7uxFWOqmEcfYmwdH73w6W6pMB8Olp2Ta BvzMJJlivTX8vieGiBO/3iU7/QT+EhM6RbbjvMDehlDdy+I/bWtVhmy9lPbRbWVw TYL9j/OtLdGKY2jemOUT9mw3GeElhG9xFjmwFVGDsukQZ/wi0ZrTegY1Y3jJ+X4Y a5UxNqCVAFWrsbCLrdTf8S1NVrm3saMmkYa41yvZLxJo58/ZLcu5O5s/EcamOmDO jgDbZYZkH/11OqxEK1tOi0pZV2Q8w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedruddtfedgkedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedfpfhi khholhgruhhsucftrghthhdfuceonhhikhholhgruhhssehrrghthhdrohhrgheqnecugg ftrfgrthhtvghrnhepffdutdegvdegtddtgeekueevfeelgfejleetudegieelhfdtvefg jeejffefkedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepnhhikhholhgruhhssehrrghthhdrohhrgh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 1CDC9180091; Sun, 17 May 2020 11:00:54 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.0-dev0-413-g750b809-fmstable-20200507v1 Mime-Version: 1.0 Message-Id: In-Reply-To: <20200517080909.lod7sjfio5jvsjr3@yavin.dot.cyphar.com> References: <874kshqa1d.fsf@vostro.rath.org> <20200517080909.lod7sjfio5jvsjr3@yavin.dot.cyphar.com> Date: Sun, 17 May 2020 15:59:08 +0100 From: "Nikolaus Rath" To: "Linux FS Devel" Subject: Re: [fuse-devel] Determining owner of a (fuse) mountpoint? Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Sun, 17 May 2020, at 09:09, Aleksa Sarai wrote: > On 2020-05-15, Nikolaus Rath wrote: > > Given a (FUSE) mountpoint (potentially mounted without -o allow_root= ), > > is there a way for root to determine its "owner" (i.e. the user who = has > > started the FUSE process and invoked fusermount) that does not depen= d on > > cooperation of the user/filesystem? >=20 > The mount options of a FUSE mount contain the entries "user_id=3DN" an= d > "group_id=3DM" which correspond to the "mount owner" and those entries= are > filled by fusermount. Is that not sufficient? I think it is sufficient, I just never noticed it. Thanks! Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2=AB