Displaying 1 result from an estimated 1 matches for "oom_reap_task_mm".
Did you mean:
__oom_reap_task_mm
2019 Sep 06
0
possible deadlock in __mmu_notifier_invalidate_range_end
...---------------
oom_reaper/1065 is trying to acquire lock:
ffffffff8904ff60 (mmu_notifier_invalidate_range_start){+.+.}, at:
__mmu_notifier_invalidate_range_end+0x0/0x360 mm/mmu_notifier.c:169
but task is already holding lock:
ffffffff8904ff60 (mmu_notifier_invalidate_range_start){+.+.}, at:
__oom_reap_task_mm+0x196/0x490 mm/oom_kill.c:542
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(mmu_notifier_invalidate_range_start);
lock(mmu_notifier_invalidate_range_start);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 l...