From: Lennart Poettering Date: Wed, 24 Mar 2021 13:06:22 +0000 (+0100) Subject: mount-util: extend comment a bit, mention that we aren't atomic in behaviour X-Git-Tag: v249-rc1~502^2~6 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=4b6ef52756ce1be1bd365c2bb63ad4f0c895c1a5;p=thirdparty%2Fsystemd.git mount-util: extend comment a bit, mention that we aren't atomic in behaviour --- diff --git a/src/shared/mount-util.c b/src/shared/mount-util.c index fb7e513acc5..778cfba1ea9 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. */