SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

namespace: extend bind mount ignore field to permission issues

Browse Source 
A later commit will add transient allocation of user namespaces with
dynamic UID range assignment. That creates certain permission issues.
Let's hence allow them to be handled gracefully in case the 'ignore'
field is set for a mount.
This commit is contained in:
Lennart Poettering
2026-02-19 15:07:19 +01:00
parent 26f80a9d33
commit fe487d3670
2 changed files with 23 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/systemd.exec.xml
+10 -10
View File
@@ -450,16 +450,16 @@
<term><varname>BindPaths=</varname></term>
<term><varname>BindReadOnlyPaths=</varname></term>
<listitem><para>Configures unit-specific bind mounts. A bind mount makes a particular file or directory
available at an additional place in the unit's view of the file system. Any bind mounts created with this
option are specific to the unit, and are not visible in the host's mount table. This option expects a
whitespace separated list of bind mount definitions. Each definition consists of a colon-separated triple of
source path, destination path and option string, where the latter two are optional. If only a source path is
specified the source and destination is taken to be the same. The option string may be either
<literal>rbind</literal> or <literal>norbind</literal> for configuring a recursive or non-recursive bind
mount. If the destination path is omitted, the option string must be omitted too.
Each bind mount definition may be prefixed with <literal>-</literal>, in which case it will be ignored
when its source path does not exist.</para>
<listitem><para>Configures unit-specific bind mounts. A bind mount makes a particular file or
directory available at an additional place in the unit's view of the file system. Any bind mounts
created with this option are specific to the unit, and are not visible in the host's mount
table. This option expects a whitespace separated list of bind mount definitions. Each definition
consists of a colon-separated triple of source path, destination path and option string, where the
latter two are optional. If only a source path is specified the source and destination is taken to be
the same. The option string may be either <literal>rbind</literal> or <literal>norbind</literal> for
configuring a recursive or non-recursive bind mount. If the destination path is omitted, the option
string must be omitted too. Each bind mount definition may be prefixed with <literal>-</literal>, in
which case it will be ignored when its source path does not exist or is not accessible.</para>
<para><varname>BindPaths=</varname> creates regular writable bind mounts (unless the source file system mount
is already marked read-only), while <varname>BindReadOnlyPaths=</varname> creates read-only bind mounts. These
src/core/namespace.c
+13 -5
View File
@@ -2016,12 +2016,20 @@ static int apply_one_mount(
}
r = chase(mount_entry_source(m), NULL, CHASE_TRAIL_SLASH|CHASE_TRIGGER_AUTOFS, &chased, NULL);
if (r == -ENOENT && m->ignore) {
log_debug_errno(r, "Path %s does not exist, ignoring.", mount_entry_source(m));
return 0;
}
if (r < 0)
if (r < 0) {
if (m->ignore) {
if (r == -ENOENT) {
log_debug_errno(r, "Path '%s' does not exist, ignoring.", mount_entry_source(m));
return 0;
}
if (ERRNO_IS_NEG_PRIVILEGE(r)) {
log_debug_errno(r, "Path '%s' is not accessible, ignoring: %m", mount_entry_source(m));
return 0;
}
}
return log_debug_errno(r, "Failed to follow symlinks on %s: %m", mount_entry_source(m));
}
log_debug("Followed source symlinks %s %s %s.",
mount_entry_source(m), glyph(GLYPH_ARROW_RIGHT), chased);