diff options
| author | Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp> | 2023-05-11 22:47:32 +0900 |
|---|---|---|
| committer | Thomas Gleixner <tglx@linutronix.de> | 2023-05-22 14:52:58 +0200 |
| commit | eb799279fb1f9c63c520fe8c1c41cb9154252db6 (patch) | |
| tree | b08af898ed7e318df35b97abb6650f5efdcfdaf8 /kernel/locking | |
| parent | 0cce06ba859a515bd06224085d3addb870608b6d (diff) | |
| download | linux-eb799279fb1f9c63c520fe8c1c41cb9154252db6.tar.gz linux-eb799279fb1f9c63c520fe8c1c41cb9154252db6.tar.bz2 linux-eb799279fb1f9c63c520fe8c1c41cb9154252db6.zip | |
debugobjects: Don't wake up kswapd from fill_pool()
syzbot is reporting a lockdep warning in fill_pool() because the allocation
from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM)
and therefore tries to wake up kswapd, which acquires kswapd_wait::lock.
Since fill_pool() might be called with arbitrary locks held, fill_pool()
should not assume that acquiring kswapd_wait::lock is safe.
Use __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for
!__GFP_DIRECT_RECLAIM allocation.
Fixes: 3ac7fe5a4aab ("infrastructure to debug (dynamic) objects")
Reported-by: syzbot <syzbot+fe0c72f0ccbb93786380@syzkaller.appspotmail.com>
Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/6577e1fa-b6ee-f2be-2414-a2b51b1c5e30@I-love.SAKURA.ne.jp
Closes: https://syzkaller.appspot.com/bug?extid=fe0c72f0ccbb93786380
Diffstat (limited to 'kernel/locking')
0 files changed, 0 insertions, 0 deletions