remounting root read-only in private mount namespace affects main namespace
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
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)
---
ApportVersion: 2.0.1-0ubuntu17.7
Architecture: amd64
DistroRelease: Ubuntu 12.04
MarkForUpload: True
NonfreeKernelMo
Package: linux (not installed)
Tags: precise
Uname: Linux 3.4.0-030400-
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to precise on 2012-10-06 (784 days ago)
UserGroups:
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1397649
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.