This bug occurs because apparmor is using the kernel macro
can_write_lock()
in its AA_DEBUG asserts, however can_write_lock() does not work on non-
smp kernels as the lock variable that is being tested is never updated,
as the lock operations are removed.
** Changed in: linux-goldfish (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: linux-goldfish (Ubuntu)
Status: New => Confirmed
** Also affects: linux-goldfish (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: linux-goldfish (Ubuntu Trusty)
Importance: Undecided
Assignee: John Johansen (jjohansen)
Status: Confirmed
** Changed in: linux-goldfish (Ubuntu Saucy)
Status: New => Confirmed
** Changed in: linux-goldfish (Ubuntu Saucy)
Assignee: (unassigned) => John Johansen (jjohansen)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253707
Title:
apparmor backtraces for goldfish kernel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-goldfish/+bug/1253707/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
