kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc7-vivid/

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1397649

Title:
  remounting root read-only in private mount namespace affects main
  namespace

Status in linux package in Ubuntu:
  Incomplete

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
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  Tags:  precise
  Uname: Linux 3.4.0-030400-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to precise on 2012-10-06 (784 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397649/+subscriptions