From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Leo Famulari <leo@famulari.name>, 53407@debbugs.gnu.org
Subject: bug#53407: libfuse 3 can't find fusermount
Date: Fri, 21 Jan 2022 08:55:23 +0100 [thread overview]
Message-ID: <f6678af305390ab15fbc25005c7642222dd08e40.camel@ist.tugraz.at> (raw)
In-Reply-To: <YepjvRmfZf2tNtuo@jasmine.lan>
Hi Leo,
Am Freitag, dem 21.01.2022 um 02:41 -0500 schrieb Leo Famulari:
> While testing a Borg update (patch attached), I noticed that the
> FUSERMOUNT_DIR hack in Fuse 3 doesn't seem to work like it does with
> Fuse 2.
>
> The 1.2.0b3 beta of the upcoming Borg release can use either Fuse 2
> (with python-llfuse) or Fuse 3 (with python-pyfuse3).
>
> The `borg mount` command works as expected with Fuse 2 / llfuse.
>
> But, with Fuse 3 / pyfuse3, it fails with:
>
> fuse: failed to exec fusermount3: No such file or directory
>
> When I commented out the FUSERMOUNT_DIR [0] substitution in the fuse-
> 3 package and rebuilt Borg, `borg mount` instead gives us this, which
> is expected, because this system does not have a setuid fusermount3:
>
> fusermount3: mount failed: Operation not permitted
>
> So, the substitution doesn't seem to help with Fuse 3: it just breaks
> the lookup.
>
> You can apply the patch and test it out. And you can also observe the
> optimal behaviour if you switch the borg package's fuse
> implementation from pyfuse3 to llfuse / Fuse 2.
>
> Should we just remove the substitution in fuse-3?
What is the behaviour if you have fusermount3 setuid? I know from gvfs
(which also depends on Fuse 3), that adding the setuid binary *does*
make gvfsd-fuse work again, so it'd be good to know if this works for
borg as well. If not, we'd have to be careful not to introduce a
regression.
Cheers
next prev parent reply other threads:[~2022-01-21 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 7:41 bug#53407: libfuse 3 can't find fusermount Leo Famulari
2022-01-21 7:55 ` Liliana Marie Prikler [this message]
2022-01-21 17:17 ` Leo Famulari
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=f6678af305390ab15fbc25005c7642222dd08e40.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=53407@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.