Public bug reported:
When remounting root read-only in a private mount namespace, then also
the real root (in default namespace) is read-only.
However, it is then possible to remount the real root read-write, and
this doesn't (fortunately...) affect the other namespace.
How to reproduce:
-----------------------------
(in one console):
# unshare --mount /bin/bash
# mount -o remount -r /
(in other console)
# touch /x
touch: cannot touch `/x': Read-only file system
# mount -o remount -w /
# touch /x
(in first console)
# touch /x
touch: cannot touch `/x': Read-only file system
What happened:
--------------------------
Read-only mount performed in private mount namespace affected main (default)
namespace
What should have happened:
-----------------------------------------------
The read-only mount should not have affected the main namespace
(this has been seen in 3.0.0 and also 3.4.0 on precise)
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397649
Title:
remounting root read-only in private mount namespace affects main
namespace
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397649/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
