← Back to team overview

kernel-packages team mailing list archive

[Bug 1397649] Missing required logs.


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.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  remounting root read-only in private mount namespace affects main

Status in linux package in Ubuntu:

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)

To manage notifications about this bug go to: