All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: fuse-devel@lists.sourceforge.net, miklos <mszeredi@redhat.com>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Determining owner of a (fuse) mountpoint?
Date: Fri, 15 May 2020 20:21:18 +0100	[thread overview]
Message-ID: <874kshqa1d.fsf@vostro.rath.org> (raw)

Hello,

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 depend on
cooperation of the user/filesystem?

Best,
-Nikolaus

-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

             reply	other threads:[~2020-05-15 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 19:21 Nikolaus Rath [this message]
2020-05-17  8:09 ` Determining owner of a (fuse) mountpoint? Aleksa Sarai
2020-05-17 14:59   ` [fuse-devel] " Nikolaus Rath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874kshqa1d.fsf@vostro.rath.org \
    --to=nikolaus@rath.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mszeredi@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.