diff options
| author | John Johansen <john.johansen@canonical.com> | 2022-09-06 12:39:55 +0200 |
|---|---|---|
| committer | John Johansen <john.johansen@canonical.com> | 2022-10-03 23:49:02 +0200 |
| commit | 9c4557efc558a68e4cd973490fd936d6e3414db8 (patch) | |
| tree | 82da3e649815cac3d7b88bad98bb8e3f731fc2fd /Kconfig | |
| parent | apparmor: fix a memleak in multi_transaction_new() (diff) | |
| download | linux-9c4557efc558a68e4cd973490fd936d6e3414db8.tar.xz linux-9c4557efc558a68e4cd973490fd936d6e3414db8.zip | |
apparmor: fix lockdep warning when removing a namespace
Fix the following lockdep warning
[ 1119.158984] ============================================
[ 1119.158988] WARNING: possible recursive locking detected
[ 1119.158996] 6.0.0-rc1+ #257 Tainted: G E N
[ 1119.158999] --------------------------------------------
[ 1119.159001] bash/80100 is trying to acquire lock:
[ 1119.159007] ffff88803e79b4a0 (&ns->lock/1){+.+.}-{4:4}, at: destroy_ns.part.0+0x43/0x140
[ 1119.159028]
but task is already holding lock:
[ 1119.159030] ffff8881009764a0 (&ns->lock/1){+.+.}-{4:4}, at: aa_remove_profiles+0x3f0/0x640
[ 1119.159040]
other info that might help us debug this:
[ 1119.159042] Possible unsafe locking scenario:
[ 1119.159043] CPU0
[ 1119.159045] ----
[ 1119.159047] lock(&ns->lock/1);
[ 1119.159051] lock(&ns->lock/1);
[ 1119.159055]
*** DEADLOCK ***
Which is caused by an incorrect lockdep nesting notation
Fixes: feb3c766a3ab ("apparmor: fix possible recursive lock warning in __aa_create_ns")
Signed-off-by: John Johansen <john.johansen@canonical.com>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions