shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-25 23:21:33 +03:00
Code
643006f62b
systemd-stable/units/sys-fs-fuse-connections.mount

33 lines
1.1 KiB
SYSTEMD
Raw Normal View History

license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09 07:23:58 +03:00
# SPDX-License-Identifier: LGPL-2.1-or-later
Add SPDX license headers to unit files
2017-11-18 19:35:03 +03:00
#
units: introduce unit file for FUSE fs FUSE and configfs is very very similar, so handle both the same way.
2011-09-22 05:00:04 +04:00
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
relicense to LGPLv2.1 (with exceptions) We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends.
2012-04-12 02:20:58 +04:00
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
units: introduce unit file for FUSE fs FUSE and configfs is very very similar, so handle both the same way.
2011-09-22 05:00:04 +04:00
# (at your option) any later version.
[Unit]
Description=FUSE Control File System
man: add Documentation= tags to all kinds of missing units
2012-06-27 03:07:04 +04:00
Documentation=https://www.kernel.org/doc/Documentation/filesystems/fuse.txt
units: use https for the freedesktop url (#6227)
2017-06-29 05:54:12 +03:00
Documentation=https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
units: introduce unit file for FUSE fs FUSE and configfs is very very similar, so handle both the same way.
2011-09-22 05:00:04 +04:00
DefaultDependencies=no
units: restore sysfs conditions in sys-fs-fuse-connections.mount and sys-kernel-config.mount Commit 42cc2855ba2fe4c6f5d incorrectly removed the condition on sysfs in both sys-fs-fuse-connections.mount and sys-kernel-config.mount. However there are still needed in case modprobe of one of these modules is intentionally skipped (due to lack of privs for example). This patch restores the 2 conditions which should be safe for the common case, since all conditions are only checked after all deps ordered before are complete. Follow-up for 42cc2855ba2fe4c6f5dc863507a1c843611350a0.
2020-11-20 13:52:36 +03:00
ConditionPathExists=/sys/fs/fuse/connections
units: don't try to mount the FUSE fs if we lack the privileges for it See: https://lists.freedesktop.org/archives/systemd-devel/2016-February/035740.html
2016-02-11 01:02:53 +03:00
ConditionCapability=CAP_SYS_ADMIN
units: disable /sys/fs/fuse/connections in private user namespaces (#4592) The mount fails, even though CAP_SYS_ADMIN is granted. Only file systems with FU_USERNS_MOUNT in .fs_flags may be mounted in userns, and the patch to add that fusectl was rejected [1]. It would be nice if we could check if the kernel has FU_USERNS_MOUNT for a given fs type, since this could change over time, but this information doesn't seem to be exported. So let's just skip this mount in userns to avoid an error during boot. [1] https://patchwork.kernel.org/patch/2828269/
2016-11-11 21:00:33 +03:00
ConditionVirtualization=!private-users
units: introduce unit file for FUSE fs FUSE and configfs is very very similar, so handle both the same way.
2011-09-22 05:00:04 +04:00
Before=sysinit.target
units: wait until some fs modules are entirely loaded before mounting their corresponding filesystem udev requests to start the fs mount units when their respective module is loaded. For that it monitors uevents of type "ADD" for the relevant fs modules. However the uevent is sent by the kernel too early, ie before the init() of the module is called hence before directories in /sys/fs/ are created. This patch workarounds adds "Requires/After=modprobe@<fs-module>.service" to the mount unit, which means that modprobe(8) will be called once the fs module is announced to be loaded. This sounds pointless, but given that modprobe only returns after the initialization of the module is complete, it should workaround the issue. As a side effect, the module will be automatically loaded if the mount unit is started manually. Fixes #17586.
2020-11-19 11:17:19 +03:00
# These dependencies are used to make certain that the module is fully
# loaded. Indeed udev starts this unit when it receives an uevent for the
# module but the kernel sends it too early, ie before the init() of the module
# is fully operational and /sys/fs/fuse/connections is created, see issue#17586.
After=modprobe@fuse.service
Requires=modprobe@fuse.service
units: introduce unit file for FUSE fs FUSE and configfs is very very similar, so handle both the same way.
2011-09-22 05:00:04 +04:00
[Mount]
What=fusectl
Where=/sys/fs/fuse/connections
Type=fusectl
units: set nodev,nosuid,noexec flags for various secondary API VFS A couple of API VFS we mount via .mount units. Let's set the three flags for those too, just in case. This is just paranoia, nothing else, but shouldn't hurt.
2019-03-25 21:39:00 +03:00
Options=nosuid,nodev,noexec
Copy Permalink