This bug was fixed in the package linux - 4.13.0-11.12
---
linux (4.13.0-11.12) artful; urgency=low
* linux: 4.13.0-11.12 -proposed tracker (LP: #1716699)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: fix local TLB flushing vs. detach
** Changed in: linux (Ubuntu)
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/1713103
Title:
snapd 2.27.3+17.10 ADT test failure with linux
sort of. The code was broken into patches and upstreamed piece meal, so
the tighter restrictions when a give patch went it made sense. They also
better reflect some of the internal permissions that were being
enforced, ie. while profiles was you needed cap mac admin to actual
see it. It looks
@jjohansen are the more restrictive file permissions intentional? I see
quite a few apparmorfs permissions changes between xenial and upstream:
-static struct aa_fs_entry aa_fs_entry_apparmor[] = {
- AA_FS_FILE_FOPS(".access", 0666, _fs_access),
- AA_FS_FILE_FOPS(".stacked", 0666,
The apparmorfs kernel query interface file has more restrictive file
permissions in the upstream kernel versus what we've had in the Ubuntu
sauce patches.
In Artful (Ubuntu 4.11.0-13.19-generic 4.11.12):
$ ls -al /sys/kernel/security/apparmor/.access
-rw-rw-rw- 1 root root 0 Aug 15 17:38
5 matches
Mail list logo
