Am 08.02.21 um 23:42 schrieb Mike Gilbert:
On Mon, Feb 8, 2021 at 2:31 PM Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
I think removing this symlink would prevent /sys/fs/fuse/connections
from being mounted and the fuse module from being loaded
unconditionally on boot
no
https://bugzilla.redhat.com/show_bug.cgi?id=1909805#c6
It almost works for me on Gentoo Linux.
To test, I first had to reconfigure my kernel to build FUSE as a
module (I normally have it built-in).
I then removed the sys-fs-fuse-connections.mount symlink from
sysinit.target.wants.
After rebooting with the new kernel, the FUSE module is not loaded and
/sys/fs/fuse/connections is not mounted.
Unfortunately, mounting FUSE-based file systems does not work until I
manually run "modprobe fuse".
It seems that my kernel does not auto-load the module, despite the
static /dev/fuse node. The kernel is probably missing a call to
__request_module().
Given that the kernel doesn't auto-load the module on demand, leaving
the sysinit.target.wants symlink in place seems like the safe thing to
do.
but for sure not on a stripped down machine running a iptables-nft
ruleset, a socket-activated sshd and nohting else
if it's me for server setups the "fuse" kernel-module could be in
"kernel-modules" which is not installed and needed for virtualized guests
the point is that all this setups where happy without fuse loaded from
2008 to 2021 and you can't even avoid it with F33 at all, no matter what
you delete or mask
a active masked unit - seriously? :-)
[root@rawhide ~]# systemctl status sys-module-fuse.device
sys-fs-fuse-connections.mount
● sys-module-fuse.device - /sys/module/fuse
Loaded: masked (Reason: Unit sys-module-fuse.device is masked.)
Active: active (plugged) since Mon 2021-02-08 19:33:18 CET; 1min
42s ago
Device: /sys/module/fuse
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
