syzbot


BUG: scheduling while atomic in exit_to_user_mode_loop

Status: upstream: reported C repro on 2025/05/25 06:17
Reported-by: syzbot+eb504c1673110fdd427e@syzkaller.appspotmail.com
First crash: 61d, last: 4d21h
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream BUG: scheduling while atomic in exit_to_user_mode_loop ntfs3 5 syz error error 1 993d 1020d 0/29 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 5 C done 3 519d 572d 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:upstream 5 C done 822 40d 573d 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 5 C done 1087 391d 572d 0/2 auto-obsoleted due to no activity on 2024/09/07 07:43
linux-5.15 BUG: scheduling while atomic in exit_to_user_mode_loop origin:lts-only 5 syz unreliable 2 522d 528d 0/3 auto-obsoleted due to no activity on 2024/10/07 06:36
Last patch testing requests (1)
Created Duration User Patch Repo Result
2025/06/08 08:00 9m retest repro android13-5.10-lts report log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/07/08 12:44 1h07m bisect fix android13-5.10-lts OK (0) job log log

Sample crash report:
loop2: rw=524288, want=72, limit=16
attempt to access beyond end of device
loop2: rw=524288, want=1183600, limit=16
attempt to access beyond end of device
loop2: rw=524288, want=1048976, limit=16
attempt to access beyond end of device
loop2: rw=524288, want=672, limit=16
attempt to access beyond end of device
loop2: rw=524288, want=3670472, limit=16
attempt to access beyond end of device
loop2: rw=524288, want=790384, limit=16
attempt to access beyond end of device
loop2: rw=524288, want=14425508768, limit=16
BUG: scheduling while atomic: syz.2.16/357/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff82120c40>] kmap_atomic include/linux/highmem.h:156 [inline]
[<ffffffff82120c40>] z_erofs_reload_indexes+0x1d0/0x450 fs/erofs/zmap.c:132
CPU: 0 PID: 357 Comm: syz.2.16 Not tainted 5.10.239-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 __dump_stack+0x21/0x24 lib/dump_stack.c:77
 dump_stack_lvl+0x169/0x1d8 lib/dump_stack.c:118
 dump_stack+0x15/0x1c lib/dump_stack.c:135
 __schedule_bug+0x177/0x230 kernel/sched/core.c:4545
 schedule_debug kernel/sched/core.c:4572 [inline]
 __schedule+0xc33/0x1310 kernel/sched/core.c:4700
 schedule+0x13c/0x1d0 kernel/sched/core.c:4884
 exit_to_user_mode_loop+0x4b/0xe0 kernel/entry/common.c:160
 exit_to_user_mode_prepare kernel/entry/common.c:199 [inline]
 syscall_exit_to_user_mode+0x68/0x90 kernel/entry/common.c:274
 do_syscall_64+0x3d/0x40 arch/x86/entry/common.c:56
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f4bbd6009a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fffe56e5bd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000dd
RAX: 0000000000000000 RBX: 00007f4bbd827fa0 RCX: 00007f4bbd6009a9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007f4bbd682d69 R08: 000000000000000

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/20 14:03 android13-5.10-lts 6de38b5f6c2b 7117feec .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 BUG: scheduling while atomic in exit_to_user_mode_loop
2025/05/25 06:15 android13-5.10-lts 7e2543346ff7 ed351ea7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 BUG: scheduling while atomic in exit_to_user_mode_loop
2025/05/25 06:01 android13-5.10-lts 7e2543346ff7 ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 BUG: scheduling while atomic in exit_to_user_mode_loop
2025/05/25 06:01 android13-5.10-lts 7e2543346ff7 ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 BUG: scheduling while atomic in exit_to_user_mode_loop
2025/05/25 06:01 android13-5.10-lts 7e2543346ff7 ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 BUG: scheduling while atomic in exit_to_user_mode_loop
2025/05/25 06:01 android13-5.10-lts 7e2543346ff7 ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 BUG: scheduling while atomic in exit_to_user_mode_loop
* Struck through repros no longer work on HEAD.