diff options
| author | Yu Watanabe <watanabe.yu+github@gmail.com> | 2023-05-22 23:36:44 +0200 |
|---|---|---|
| committer | Yu Watanabe <watanabe.yu+github@gmail.com> | 2023-05-26 04:50:08 +0200 |
| commit | a60f96fcf55c3452e5b13d6daec537af1909eda3 (patch) | |
| tree | a9d1d2ccbc3bcc8dae98443b4cb613c109a00ff6 /man/systemd.unit.xml | |
| parent | core/unit: drop doubled empty line (diff) | |
| download | systemd-a60f96fcf55c3452e5b13d6daec537af1909eda3.tar.xz systemd-a60f96fcf55c3452e5b13d6daec537af1909eda3.zip | |
core/unit: make JoinsNamespaceOf= implies the inverse dependency
Previously, even if a.service has JoinsNamespaceOf=b.service, the
inverse direction of reference was not introduced.
Hence, a.service is started earlier than b.service, the namespace will
not shared with b.service.
Also, even if a.service had the reference to b.service, b.service did not.
If b.service is freed earlier, then unit_clear_dependencies() does not clear
the reference from a to b, and will cause use-after-free on unit_free() for
a.service.
Let's make JoinsNamespaceOf=b.service in a.service implies the inverse
dependency, i.e. JoinsNamespaceOf=a.service for b.service. Then, we can safely
free b.service.
Diffstat (limited to 'man/systemd.unit.xml')
| -rw-r--r-- | man/systemd.unit.xml | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index d603ec9744..fcd1f914a8 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -856,16 +856,18 @@ <term><varname>JoinsNamespaceOf=</varname></term> <listitem><para>For units that start processes (such as service units), lists one or more other units - whose network and/or temporary file namespace to join. This only applies to unit types which support - the <varname>PrivateNetwork=</varname>, <varname>NetworkNamespacePath=</varname>, + whose network and/or temporary file namespace to join. If this is specified on a unit (say, a.service + has <varname>JoinsNamespaceOf=b.service</varname>), then this the inverse dependency + (<varname>JoinsNamespaceOf=a.service</varname> for b.service) is implied. This only applies to unit + types which support the <varname>PrivateNetwork=</varname>, <varname>NetworkNamespacePath=</varname>, <varname>PrivateIPC=</varname>, <varname>IPCNamespacePath=</varname>, and <varname>PrivateTmp=</varname> directives (see <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details). If a unit that has this setting set is started, its processes will see the same <filename>/tmp/</filename>, <filename>/var/tmp/</filename>, IPC namespace and network namespace as - one listed unit that is started. If multiple listed units are already started, it is not defined - which namespace is joined. Note that this setting only has an effect if - <varname>PrivateNetwork=</varname>/<varname>NetworkNamespacePath=</varname>, + one listed unit that is started. If multiple listed units are already started and these do not share + their namespace, then it is not defined which namespace is joined. Note that this setting only has an + effect if <varname>PrivateNetwork=</varname>/<varname>NetworkNamespacePath=</varname>, <varname>PrivateIPC=</varname>/<varname>IPCNamespacePath=</varname> and/or <varname>PrivateTmp=</varname> is enabled for both the unit that joins the namespace and the unit whose namespace is joined.</para></listitem> |