From the PR:
Currently, if there are two /proc/self/mountinfo entries with the same
mount point path, the mount setup flags computed for the second of
these two entries will overwrite the mount setup flags computed for
the first of these two entries. This is the root cause of issue #7798.
This patch changes mount_setup_existing_unit to prevent the
just_mounted mount setup flag from being overwritten if it is set to
true. This will allow all mount units created from /proc/self/mountinfo
entries to be initialized properly.
From the PR: mountinfo entries with the same existing_ unit to prevent the mountinfo
Currently, if there are two /proc/self/
mount point path, the mount setup flags computed for the second of
these two entries will overwrite the mount setup flags computed for
the first of these two entries. This is the root cause of issue #7798.
This patch changes mount_setup_
just_mounted mount setup flag from being overwritten if it is set to
true. This will allow all mount units created from /proc/self/
entries to be initialized properly.
One line fix in https:/ /github. com/systemd/ systemd/ pull/7811/ files
Referenced issue: https:/ /github. com/systemd/ systemd/ issues/ 7798
Related kubernetes issue: https:/ /github. com/kubernetes/ kubernetes/ issues/ 57345
systemd v237 has this fix, but we'd like to have it fixed in 16.04.