syzbot


BUG: sleeping function called from invalid context in kvm_mmu_notifier_invalidate_range_start

Status: upstream: reported on 2025/12/08 07:41
Subsystems: mm
[Documentation on labels]
Reported-by: syzbot+c3178b6b512446632bac@syzkaller.appspotmail.com
First crash: 97d, last: 6d11h
✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision Error
30b82e8d-78dd-458a-b1aa-fa15a1dbed4d repro BUG: sleeping function called from invalid context in kvm_mmu_notifier_invalidate_range_start 2026/03/08 15:18 2026/03/08 15:18 2026/03/08 15:26 31e9c887f7dc24e04b3ca70d0d54fc34141844b0
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [mm?] BUG: sleeping function called from invalid context in kvm_mmu_notifier_invalidate_range_start 0 (1) 2025/12/08 07:41

Sample crash report:
BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48
in_atomic(): 0, irqs_disabled(): 0, non_block: 1, pid: 39, name: oom_reaper
preempt_count: 0, expected: 0
RCU nest depth: 0, expected: 0
4 locks held by oom_reaper/39:
 #0: ffff888026d669b0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_trylock include/linux/mmap_lock.h:611 [inline]
 #0: ffff888026d669b0 (&mm->mmap_lock){++++}-{4:4}, at: oom_reap_task_mm mm/oom_kill.c:582 [inline]
 #0: ffff888026d669b0 (&mm->mmap_lock){++++}-{4:4}, at: oom_reap_task mm/oom_kill.c:625 [inline]
 #0: ffff888026d669b0 (&mm->mmap_lock){++++}-{4:4}, at: oom_reaper+0x29e/0xae0 mm/oom_kill.c:666
 #1: ffffffff8df04b60 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at: mmu_notifier_invalidate_range_start_nonblock include/linux/mmu_notifier.h:456 [inline]
 #1: ffffffff8df04b60 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at: __oom_reap_task_mm+0x2c7/0x570 mm/oom_kill.c:558
 #2: ffffffff8df04bb8 (srcu){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:187 [inline]
 #2: ffffffff8df04bb8 (srcu){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:294 [inline]
 #2: ffffffff8df04bb8 (srcu){.+.+}-{0:0}, at: mn_hlist_invalidate_range_start mm/mmu_notifier.c:468 [inline]
 #2: ffffffff8df04bb8 (srcu){.+.+}-{0:0}, at: __mmu_notifier_invalidate_range_start+0x30b/0x840 mm/mmu_notifier.c:533
 #3: ffff88805e7b4af8 (&kvm->mn_invalidate_lock){+.+.}-{3:3}, at: spin_lock include/linux/spinlock_rt.h:45 [inline]
 #3: ffff88805e7b4af8 (&kvm->mn_invalidate_lock){+.+.}-{3:3}, at: kvm_mmu_notifier_invalidate_range_start+0x1b7/0xc30 virt/kvm/kvm_main.c:749
CPU: 0 UID: 0 PID: 39 Comm: oom_reaper Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 __might_resched+0x329/0x480 kernel/sched/core.c:8885
 __rt_spin_lock kernel/locking/spinlock_rt.c:48 [inline]
 rt_spin_lock+0xc2/0x400 kernel/locking/spinlock_rt.c:57
 spin_lock include/linux/spinlock_rt.h:45 [inline]
 kvm_mmu_notifier_invalidate_range_start+0x1b7/0xc30 virt/kvm/kvm_main.c:749
 mn_hlist_invalidate_range_start mm/mmu_notifier.c:478 [inline]
 __mmu_notifier_invalidate_range_start+0x43f/0x840 mm/mmu_notifier.c:533
 mmu_notifier_invalidate_range_start_nonblock include/linux/mmu_notifier.h:459 [inline]
 __oom_reap_task_mm+0x32a/0x570 mm/oom_kill.c:558
 oom_reap_task_mm mm/oom_kill.c:601 [inline]
 oom_reap_task mm/oom_kill.c:625 [inline]
 oom_reaper+0x3ca/0xae0 mm/oom_kill.c:666
 kthread+0x388/0x470 kernel/kthread.c:436
 ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
oom_reaper: reaped process 20558 (syz.9.4066), now anon-rss:0kB, file-rss:25812kB, shmem-rss:0kB

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/03/07 23:43 upstream 4ae12d8bd9a8 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root BUG: sleeping function called from invalid context in kvm_mmu_notifier_invalidate_range_start
2026/01/30 10:53 upstream 4d310797262f bfa73b7b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root BUG: sleeping function called from invalid context in kvm_mmu_notifier_invalidate_range_start
2025/12/07 07:33 upstream 37bb2e7217b0 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root BUG: sleeping function called from invalid context in kvm_mmu_notifier_invalidate_range_start
2025/12/07 07:25 upstream 37bb2e7217b0 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root BUG: sleeping function called from invalid context in kvm_mmu_notifier_invalidate_range_start
* Struck through repros no longer work on HEAD.