This bug was fixed in the package linux - 4.2.0-38.45
---
linux (4.2.0-38.45) wily; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs: forbid
This bug was fixed in the package linux-lts-utopic -
3.16.0-73.95~14.04.1
---
linux-lts-utopic (3.16.0-73.95~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesys
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs: forbi
This bug was fixed in the package linux - 3.19.0-61.69
---
linux (3.19.0-61.69) vivid; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs: forb
This bug was fixed in the package linux - 3.13.0-87.133
---
linux (3.13.0-87.133) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1585315
[ Upstream Kernel Changes ]
* Revert "usb: hub: do not clear BOS field during reset device"
- LP: #1582864
This bug was fixed in the package linux - 4.4.0-23.41
---
linux (4.4.0-23.41) xenial; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1582431
* zfs: disable module checks for zfs when cross-compiling (LP: #1581127)
- [Packaging] disable zfs module checks wh
Verified that the problem is fixed in all four kernels.
** Tags removed: verification-needed-trusty verification-needed-vivid
verification-needed-wily verification-needed-xenial
** Tags added: verification-done-trusty verification-done-vivid
verification-done-wily verification-done-xenial
--
Y
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from today
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Vivid)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: In P
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1572316
Title:
oops when propagating mounts in
** Description changed:
+ SRU Justification:
+
+ Impact: Propagation to some mount tree configurations can cause the
+ kernel to oops. This is trivially reproducible using lxd.
+
+ Fix: Cherry pick from upstream user-namespace.git tree. Pull request
+ into Linus' tree is pending.
+
+ Regression
Fix sent to Linus:
http://lkml.kernel.org/r/87zis4wna1.fsf...@x220.int.ebiederm.org
I've tested this on xenial and it fixes the oops. I'll send out patches
shortly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
** Summary changed:
- oops when propagating mounts into containers
+ oops when propagating mounts into containers - RIP: 0010:[]
[] propagate_one+0xbe/0x1c0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Hi, I'm having a kernel oops with similar trace, but for me it happens at login
time. Maybe there's an automatic mount.
Mine is https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578325
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
This doesn't have to be an nfs mount, I've been able to reproduce it
using an ext4 loopback mount.
--
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/1572316
Title:
oops when propagating mou
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
** Also affects: linux (Ubuntu Xenial)
Importance: High
Assignee: Seth Forshee
19 matches
Mail list logo
