syzbot


BUG: scheduling while atomic in exit_to_user_mode_loop

Status: upstream: reported syz repro on 2024/02/12 22:31
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+db9b93e900b84e1aee87@syzkaller.appspotmail.com
First crash: 80d, last: 74d
Bug presence (2)
Date Name Commit Repro Result
2024/02/12 linux-5.15.y (ToT) 6139f2a02fe0 C [report] BUG: scheduling while atomic in exit_to_user_mode_loop
2024/02/12 upstream (ToT) c664e16bb1ba C Didn't crash
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream BUG: scheduling while atomic in exit_to_user_mode_loop ntfs3 syz error error 1 544d 571d 0/26 auto-obsoleted due to no activity on 2023/05/14 09:44
linux-6.1 BUG: scheduling while atomic in exit_to_user_mode_loop origin:lts-only C done 3 71d 124d 0/3 upstream: reported C repro on 2023/12/30 14:50
android-5-15 BUG: scheduling while atomic in exit_to_user_mode_loop origin:lts C 695 6h05m 124d 0/2 upstream: reported C repro on 2023/12/30 11:04
android-6-1 BUG: scheduling while atomic in exit_to_user_mode_loop origin:lts C 868 4h40m 124d 0/2 upstream: reported C repro on 2023/12/30 11:52
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2024/02/28 17:35 6h19m fix candidate upstream job log (1)

Sample crash report:
BUG: scheduling while atomic: udevd/2963/0x00000002
no locks held by udevd/2963.
Modules linked in:
Preemption disabled at:
[<ffffffff8174f806>] is_module_text_address+0x16/0x140 kernel/module.c:4758
Kernel panic - not syncing: scheduling while atomic: panic_on_warn set ...
CPU: 1 PID: 2963 Comm: udevd Not tainted 5.15.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 panic+0x318/0x84d kernel/panic.c:309
 check_panic_on_warn+0x7e/0xa0 kernel/panic.c:229
 __schedule_bug+0x1ba/0x220 kernel/sched/core.c:5570
 schedule_debug kernel/sched/core.c:5599 [inline]
 __schedule+0x138a/0x45b0 kernel/sched/core.c:6267
 schedule+0x11b/0x1f0 kernel/sched/core.c:6459
 exit_to_user_mode_loop+0x44/0x130 kernel/entry/common.c:163
 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
 __syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
 syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
 do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f88e3b33477
Code: 10 00 00 00 44 8b 54 24 e0 48 89 44 24 c0 48 8d 44 24 d0 48 89 44 24 c8 44 89 c2 4c 89 ce bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 76 10 48 8b 15 82 69 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007fff9d8754b8 EFLAGS: 00000287 ORIG_RAX: 0000000000000101
RAX: 000000000000000d RBX: 000055c194de12c0 RCX: 00007f88e3b33477
RDX: 0000000000090800 RSI: 000055c194e016c0 RDI: 00000000ffffff9c
RBP: 000055c194e5e480 R08: 0000000000090800 R09: 000055c194e016c0
R10: 0000000000000000 R11: 0000000000000287 R12: 000055c194e016c0
R13: 00000000000000ff R14: 000055c19321e1c4 R15: 0000000000000000
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/18 23:15 linux-5.15.y 6139f2a02fe0 578f7538 .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: scheduling while atomic in exit_to_user_mode_loop
2024/02/12 22:30 linux-5.15.y 6139f2a02fe0 77b23aa1 .config console log report syz [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-perf BUG: scheduling while atomic in exit_to_user_mode_loop
* Struck through repros no longer work on HEAD.