apparmor backtraces for goldfish kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-goldfish (Ubuntu) |
Fix Released
|
Undecided
|
John Johansen | ||
Saucy |
Won't Fix
|
Undecided
|
John Johansen | ||
Trusty |
Fix Released
|
Undecided
|
John Johansen |
Bug Description
The goldfish kernel when apparmor is enable fills the logs with backtraces similar (there are several slightly different traces) to the following:
WARNING: at /build/
AppArmor WARN __aa_label_remove: (((((void)
Modules linked in:
[<c0012864>] (unwind_
[<c001e774>] (warn_slowpath_
[<c001e80c>] (warn_slowpath_
[<c01f6b84>] (__aa_label_
[<c01f75d4>] (aa_label_
[<c01f7640>] (aa_label_
[<c01f888c>] (aa_label_
[<c01ecc48>] (query_
[<c01ecdf8>] (aa_write_
[<c00d2414>] (vfs_write+
[<c00d2654>] (sys_write+
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.