public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: fuse-devel <fuse-devel@lists.linux.dev>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Bernd Schubert <bernd@bsbernd.com>
Subject: libfuse accepts subtypes with slashes in them??
Date: Tue, 21 Apr 2026 23:35:38 -0700	[thread overview]
Message-ID: <20260422063538.GD7739@frogsfrogsfrogs> (raw)

Hey everyone,

So today I noticed that this happens on Debian 13:

$ mount -t fuse./bin/ls /root/ /etc/shadow
ls: cannot access 'rw,dev,suid': No such file or directory
-rw-r----- 1 root 1345 Nov 18 10:38 /etc/shadow

ls: cannot open directory '/root': Permission denied

Uh... is that intentional?  It looks as though mount does:

execve("/sbin/mount.fuse", ["/sbin/mount.fuse", "/root", "/etc/shadow", "-o", "rw", "-t", "fuse./bin/ls"]...)

and then mount.fuse just trims off everything after the "fuse." and
does:

execve("/bin/sh", ["/bin/sh", "-c", "'/bin/ls' '/root' '/etc/shadow' '-o' 'rw,dev,suid'"]...)

with the odd output that you see above.  Is that supposed to happen?
Or should libfuse reject subtypes with path separators?

--D

                 reply	other threads:[~2026-04-22  6:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260422063538.GD7739@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=bernd@bsbernd.com \
    --cc=fuse-devel@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox