diff options
author | 2021-09-02 14:52:58 -0700 | |
---|---|---|
committer | 2021-09-03 09:58:10 -0700 | |
commit | 4f3eaf452a14ff3982f71c1ca8bdf757254231fa (patch) | |
tree | a7ce75c39635e40feca977a1c019e4af6ebf0455 /mm/backing-dev.c | |
parent | mm/debug_vm_pgtable: fix corrupted page flag (diff) | |
download | wireguard-linux-4f3eaf452a14ff3982f71c1ca8bdf757254231fa.tar.xz wireguard-linux-4f3eaf452a14ff3982f71c1ca8bdf757254231fa.zip |
mm: report a more useful address for reclaim acquisition
A recent lockdep report included these lines:
[ 96.177910] 3 locks held by containerd/770:
[ 96.177934] #0: ffff88810815ea28 (&mm->mmap_lock#2){++++}-{3:3},
at: do_user_addr_fault+0x115/0x770
[ 96.177999] #1: ffffffff82915020 (rcu_read_lock){....}-{1:2}, at:
get_swap_device+0x33/0x140
[ 96.178057] #2: ffffffff82955ba0 (fs_reclaim){+.+.}-{0:0}, at:
__fs_reclaim_acquire+0x5/0x30
While it was not useful to that bug report to know where the reclaim lock
had been acquired, it might be useful under other circumstances. Allow
the caller of __fs_reclaim_acquire to specify the instruction pointer to
use.
Link: https://lkml.kernel.org/r/20210719185709.1755149-1-willy@infradead.org
Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: Omar Sandoval <osandov@fb.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: Boqun Feng <boqun.feng@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/backing-dev.c')
0 files changed, 0 insertions, 0 deletions