** No longer affects: apparmor (Ubuntu)
** No longer affects: apparmor (Ubuntu Xenial)
** No longer affects: apparmor (Ubuntu Yakkety)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
This bug was fixed in the package linux - 4.8.0-11.12
---
linux (4.8.0-11.12) yakkety; urgency=low
* change_hat is logging failures during expected hat probing (LP: #1615893)
- SAUCE: apparmor: Fix auditing behavior for change_hat probing
* deleted files outside of the
This bug was fixed in the package linux - 4.4.0-38.57
---
linux (4.4.0-38.57) xenial; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1620658
* CIFS client: access problems after updating to kernel 4.4.0-29-generic
(LP: #1612135)
- Revert "UBUNTU: SAUCE:
I hit this problem in Trusty with kernel "Ubuntu
4.4.0-36.55~14.04.1-generic 4.4.16" and is seems to be fixed with
"Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19" from trusty-proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
AppArmor profile
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Yakkety)
I believe I have finally tracked this one down. It only occurs when an
fd is shared between 9 or more separate profile domains and one of those
profiles is removed. The removal part can happen during the apparmor
reload phase, if a profile was renamed which is more likely on touch and
snappy.
ran some 15 profile reloads with JJ's kernel (a mix of reinstalls and
restarts), could not reproduce.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
The 14.04 stable release update for apparmor 2.10.95-0ubuntu2.2 is
causing a lot of users to hit this oops during the upgrade process due
to the upgrade triggering a profile reload.
** Summary changed:
- kernel BUG on snap disconnect from within a snap
+ AppArmor profile reloading causes an
John has been working on a fix but could use some testing. Please see
comment 27.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
AppArmor profile
12 matches
Mail list logo
