** Tags added: cscc
--
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/1634753
Title:
srcname from mount rule corrupted under load
Status in AppArmor:
Invalid
Status in linux package in
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
--
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/1634753
Title:
srcname from mount rule corrupted under load
Status
** Changed in: apparmor
Status: In Progress => Invalid
--
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/1634753
Title:
srcname from mount rule corrupted under load
Status in
This bug was fixed in the package linux - 3.13.0-103.150
---
linux (3.13.0-103.150) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1644489
* Possible regression on 3.13.0-102.149~precise1 x86_64 (gce) (LP: #1644302)
- SAUCE: apparmor: delete
I have done some light testing on this, trying to develop a none snap
based test to verify it. The test is no where near as reliable as the
snappy test. I haven't been able to trigger the bug on the new kernel
yet, with the caveat that it could just be the test. I am inclined to
declare this
Now I can run snap on Trusty from lp:1616422
I tried with the steps described in the bug, but I don't know what's
that expected output:
I got this from reproducer.sh:
1300 runs
cannot change apparmor hat of the support process for mount namespace capture.
errmsg: No child processes
support
To verify this bug on Trusty, we will need to verify this one first
https://bugs.launchpad.net/ubuntu/trusty/+source/systemd/+bug/1616422
And due to snapd is not officially available on Trusty (not even in
proposed yet), I think it's ok to skip the verification task for Trusty.
Luis, can you
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
** Changed in: linux (Ubuntu Trusty)
Status: Triaged => Fix Committed
--
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/1634753
Title:
srcname from mount rule corrupted under load
This bug was fixed in the package linux - 4.4.0-45.66
---
linux (4.4.0-45.66) xenial; urgency=low
* CVE-2016-5195
- SAUCE: mm: remove gup_flags FOLL_WRITE games from __get_user_pages()
* srcname from mount rule corrupted under load (LP: #1634753)
- SAUCE: apparmor: fix
This bug was fixed in the package linux - 4.4.0-45.66
---
linux (4.4.0-45.66) xenial; urgency=low
* CVE-2016-5195
- SAUCE: mm: remove gup_flags FOLL_WRITE games from __get_user_pages()
* srcname from mount rule corrupted under load (LP: #1634753)
- SAUCE: apparmor: fix
** Description changed:
This came up in snapd spread tests but can be reproduced with:
In an i386 up to date 16.04 VM:
1. in one terminal, run this:
- $ cat changehat_reproducer.sh
+ $ cat reproducer.sh
#!/bin/sh
set -e
sudo sysctl -w kernel.printk_ratelimit=0
sudo snap
** Tags added: kernel-da-key
--
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/1634753
Title:
srcname from mount rule corrupted under load
Status in AppArmor:
In Progress
Status in
** Changed in: linux (Ubuntu Yakkety)
Status: Triaged => Invalid
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => Triaged
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Is _only_ srcname being corrupted?
Back In The Day it was common for the kernel ring buffer for messages to
overflow and overwrite messages, but of course it did not care what was
being overwritten.
The kernel ring buffer is larger now, so it should be less common, but
not impossible if the
15 matches
Mail list logo