syzbot


BUG: scheduling while atomic in unlink_anon_vmas

Status: upstream: reported C repro on 2024/04/22 04:42
Bug presence: origin:lts
[Documentation on labels]
Reported-by: syzbot+7b06b4653d350d63d705@syzkaller.appspotmail.com
First crash: 92d, last: 92d
Bug presence (3)
Date Name Commit Repro Result
2024/04/22 lts (merge base) 6139f2a02fe0 C [report] BUG: scheduling while atomic in exit_to_user_mode_loop
2024/06/06 lts (merge base) a585faf05915 C Didn't crash
2024/04/22 upstream (ToT) ed30a4a51bb1 C Didn't crash
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-6-1 BUG: scheduling while atomic in unlink_anon_vmas C done 2 45d 123d 0/2 upstream: reported C repro on 2024/03/21 21:06
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/05/06 18:39 7m retest repro android13-5.15-lts report log

Sample crash report:
BUG: scheduling while atomic: syz-executor425/316/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff8165eb4a>] is_module_text_address+0x1a/0x140 kernel/module.c:4811
CPU: 1 PID: 316 Comm: syz-executor425 Not tainted 5.15.148-syzkaller-00013-gad06eaf051cd #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
 dump_stack+0x15/0x17 lib/dump_stack.c:113
 __schedule_bug+0x195/0x260 kernel/sched/core.c:5707
 schedule_debug kernel/sched/core.c:5734 [inline]
 __schedule+0xd19/0x1590 kernel/sched/core.c:6402
 schedule+0x11f/0x1e0 kernel/sched/core.c:6595
 rwsem_down_write_slowpath+0xde4/0x1d70 kernel/locking/rwsem.c:1207
 __down_write_common kernel/locking/rwsem.c:1341 [inline]
 __down_write kernel/locking/rwsem.c:1350 [inline]
 down_write+0x29/0x30 kernel/locking/rwsem.c:1603
 lock_anon_vma_root mm/rmap.c:250 [inline]
 unlink_anon_vmas+0xf0/0x590 mm/rmap.c:407
 free_pgtables+0x137/0x280 mm/memory.c:485
 exit_mmap+0x3e7/0x6f0 mm/mmap.c:3210
 __mmput+0x95/0x310 kernel/fork.c:1179
 mmput+0x5b/0x170 kernel/fork.c:1202
 exit_mm kernel/exit.c:552 [inline]
 do_exit+0xb9c/0x2ca0 kernel/exit.c:865
 do_group_exit+0x141/0x310 kernel/exit.c:1000
 __do_sys_exit_group kernel/exit.c:1011 [inline]
 __se_sys_exit_group kernel/exit.c:1009 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1009
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f2554f57039
Code: Unable to access opcode bytes at RIP 0x7f2554f5700f.
RSP: 002b:00007ffc51646588 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f2554f57039
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 00007f2554fd32b0 R08: ffffffffffffffb8 R09: 00000000000000a0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f2554fd32b0
R13: 0000000000000000 R14: 00007f2554fd3d20 R15: 00007f2554f281d0
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/22 04:40 android13-5.15-lts ad06eaf051cd af24b050 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in unlink_anon_vmas
* Struck through repros no longer work on HEAD.