cmd/snap-update-ns: allow detaches to propagate #14545
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When snap-update-ns chooses not to reuse a mount entry it attempts to unmount it by detaching the mount entry. Before that is done the mount entry used to be switch to private propagation, so that the unmount operation was isolated.
Disable this logic so that unmounts (and detaches) propagate normally. The mount namespace of the snap is mostly switched to slaved propagation, with the sole exception of /media or /run/media, which uses bidirectional propagation by design.
This patch is experimental and is not ready for being merged yet.
Jira: https://warthogs.atlassian.net/browse/SNAPDENG-31645