============================= WARNING: suspicious RCU usage 5.13.0-rc1-syzkaller #0 Not tainted ----------------------------- kernel/sched/core.c:8304 Illegal context switch in RCU-bh read-side critical section! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 0 1 lock held by syz-executor.2/20391: #0: ffff888022ad9a18 ( &mm->mmap_lock #2 ){++++}-{3:3} , at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline] , at: do_user_addr_fault+0x285/0x1210 arch/x86/mm/fault.c:1331 stack backtrace: CPU: 0 PID: 20391 Comm: syz-executor.2 Not tainted 5.13.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:79 [inline] dump_stack+0x141/0x1d7 lib/dump_stack.c:120 ___might_sleep+0x229/0x2c0 kernel/sched/core.c:8304 process_huge_page mm/memory.c:5100 [inline] clear_huge_page+0x9c/0x560 mm/memory.c:5161 __do_huge_pmd_anonymous_page mm/huge_memory.c:608 [inline] do_huge_pmd_anonymous_page+0x60e/0x2570 mm/huge_memory.c:771 create_huge_pmd mm/memory.c:4238 [inline] __handle_mm_fault+0x2ffd/0x52c0 mm/memory.c:4473 handle_mm_fault+0x1bc/0x7e0 mm/memory.c:4600 do_user_addr_fault+0x483/0x1210 arch/x86/mm/fault.c:1390 handle_page_fault arch/x86/mm/fault.c:1475 [inline] exc_page_fault+0x9e/0x180 arch/x86/mm/fault.c:1531 asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:577 RIP: 0033:0x408c7a Code: 09 01 00 89 c5 85 c0 0f 88 f3 07 00 00 83 f8 1d 0f 8f 6a 09 00 00 48 8d 3d f3 78 0a 00 31 c0 41 bf 01 00 00 00 e8 b6 a5 ff ff 44 0f c1 3d 85 73 69 00 41 83 ff 05 7f 06 49 83 fc 1a 77 21 48 RSP: 002b:00007f2a868120c0 EFLAGS: 00010206 RAX: 0000000000000000 RBX: 000000000056bf60 RCX: 0000000000000000 RDX: 0000000000000002 RSI: 00000000004bea81 RDI: 00000000004b0560 RBP: 0000000000000003 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000024 R13: 0000000000000000 R14: 0000000020000000 R15: 0000000000000001