summaryrefslogtreecommitdiff
path: root/src/shared/mount-util.c
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2021-03-24 14:06:22 +0100
committerLennart Poettering <lennart@poettering.net>2021-03-26 11:39:37 +0100
commit4b6ef52756ce1be1bd365c2bb63ad4f0c895c1a5 (patch)
tree705495287b07060c9cdefa84af11a7f767ff5416 /src/shared/mount-util.c
parent5c5753b9ea5cc012586ae90d357d460dec4301a4 (diff)
downloadsystemd-4b6ef52756ce1be1bd365c2bb63ad4f0c895c1a5.tar.gz
mount-util: extend comment a bit, mention that we aren't atomic in behaviour
Diffstat (limited to 'src/shared/mount-util.c')
-rw-r--r--src/shared/mount-util.c4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/shared/mount-util.c b/src/shared/mount-util.c
index fb7e513acc..778cfba1ea 100644
--- a/src/shared/mount-util.c
+++ b/src/shared/mount-util.c
@@ -216,7 +216,9 @@ int bind_remount_recursive_with_mountinfo(
* access, too. When mounts are stacked on the same mount point we only care for each individual
* "top-level" mount on each point, as we cannot influence/access the underlying mounts anyway. We do
* not have any effect on future submounts that might get propagated, they might be writable
- * etc. This includes future submounts that have been triggered via autofs.
+ * etc. This includes future submounts that have been triggered via autofs. Also note that we can't
+ * operate atomically here. Mounts established while we process the tree might or might not get
+ * noticed and thus might or might not be covered.
*
* If the "deny_list" parameter is specified it may contain a list of subtrees to exclude from the
* remount operation. Note that we'll ignore the deny list for the top-level path. */