[systemd-devel] Masking mount units

Andrei Borzenkov arvidjaar at gmail.com
Wed Nov 20 07:30:02 UTC 2024


On Tue, Nov 19, 2024 at 10:55 PM Phillip Susi <phill at thesusis.net> wrote:
>
> Furthermore, it seems that the undesirable auto mounting behavior only
> happens with systemd-239 and lower.  Newer versions of systemd seem to
> have dropped this behavior by not setting the WantedBy=foo.device on the
> mount point.  I assume this change was intentional?


commit 142b8142d7bb84f07ac33fc00527a4d48ac8ef9f
Author: Tom Yan <tom.ty89 at gmail.com>
Date:   Wed Jan 9 23:35:24 2019 +0800

    mount/generators: do not make unit wanted by its device unit

    As device units will be reloaded by systemd whenever the
corresponding device generates a "changed" event, if the mount unit /
cryptsetup service is wanted by its device unit, the former can be
restarted by systemd unexpectedly after the user stopped them
explicitly. It is not sensible at all and can be considered dangerous.
Neither is the behaviour conventional (as `auto` in fstab should only
affect behaviour on boot and `mount -a`) or ever documented at all
(not even in systemd, see systemd.mount(5) and crypttab(5)).


More information about the systemd-devel mailing list