add support for bidirectional mount event propagation in /media
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snap-confine |
Fix Released
|
Critical
|
Zygmunt Krynicki | ||
snap-confine (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Xenial |
Fix Committed
|
Undecided
|
Unassigned | ||
Yakkety |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
[Impact]
The /media directory is special in that mount events propagate outward from the mount namespace used by snap applications into the main mount
namespace.
[Test Case]
The test case can be found here:
https:/
The test case is ran automatically for each pull request and for each final release. It can be reproduced manually by executing the shell commands listed in the prepare/
The commands there assume that snapd and snap-confine are installed.
No other additional setup is necessary.
[Regression Potential]
This change involved relatively complex changes in the core logic of snap-confine and while extensive testing was performed since in both core and classic environments there's always possibility of some edge case.
For inspecting the layout of the mount namespace with this feature enabled please look at
https:/
[Other Info]
* snap-confine is technically an integral part of snapd which has an SRU exception and is allowed to introduce new features and take advantage of accelerated procedure. For more information see https:/
== # Pre-SRU bug description follows # ==
Snaps such as udisks can mount anything in /media. While this works the mount is only visible to the snap that performed the operation (as it is stuck in the mount namespace).
The mount namespace should be setup up in a way that makes /media shared with the outside namespace.
Changed in snap-confine: | |
status: | Fix Committed → Fix Released |
description: | updated |
description: | updated |
tags: | added: verification-needed |
This has been fixed with the following pull request https:/ /github. com/snapcore/ snap-confine/ pull/168