============================= WARNING: suspicious RCU usage 5.12.0-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.1/14854: #0: ffff88801bcf1658 (&mm->mmap_lock#2){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline] ffff88801bcf1658 (&mm->mmap_lock#2){++++}-{3:3}, at: do_user_addr_fault+0x285/0x1210 arch/x86/mm/fault.c:1331 stack backtrace: CPU: 0 PID: 14854 Comm: syz-executor.1 Not tainted 5.12.0-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:5074 [inline] clear_huge_page+0x14c/0x560 mm/memory.c:5112 __do_huge_pmd_anonymous_page mm/huge_memory.c:607 [inline] do_huge_pmd_anonymous_page+0x60e/0x2570 mm/huge_memory.c:772 create_huge_pmd mm/memory.c:4189 [inline] __handle_mm_fault+0x2e59/0x4f70 mm/memory.c:4424 handle_mm_fault+0x1bc/0x7e0 mm/memory.c:4551 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:0x407c0a Code: 30 48 8b 34 24 48 85 f6 74 17 8b 44 24 18 0f c8 89 c0 48 89 44 24 18 48 83 fe 01 0f 85 a1 01 00 00 48 8b 44 24 10 8b 74 24 18 <89> 30 e9 d2 fc ff ff 48 8b 44 24 10 8b 10 48 8b 04 24 48 85 c0 0f RSP: 002b:0000000000a9fb60 EFLAGS: 00010246 RAX: 0000000020cab000 RBX: 0000000000970000 RCX: 0000000000000000 RDX: 26fef6fc2d9c8125 RSI: 000000000000000c RDI: 0000000001d632f0 RBP: 0000000000a9fc58 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000004 R11: 0000000000000246 R12: 0000000000057574 R13: 00000000000003e8 R14: 000000000056bf60 R15: 0000000000057553