syzbot

 sign-in | mailing list | source | docs
🐞 Open [117]
🐞 Fixed [69]
🐞 Invalid [243]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

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: 112d, last: 3h02m
▶ ▼ 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 1044d 1071d 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 571d 624d 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 825 16d 624d 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 442d 624d 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 573d 579d 0/3 auto-obsoleted due to no activity on 2024/10/07 06:36
▶ ▼ Last patch testing requests (4)
Created Duration User Patch Repo Result
2025/08/15 20:45 6m retest repro android13-5.10-lts report log
2025/08/15 20:45 5m retest repro android13-5.10-lts report log
2025/08/15 20:45 11m retest repro android13-5.10-lts report log
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:
erofs: (device loop2): mounted with root inode @ nid 36.
BUG: scheduling while atomic: syz.2.27/383/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff82123208>] kmap_atomic include/linux/highmem.h:156 [inline]
[<ffffffff82123208>] z_erofs_reload_indexes+0x318/0x450 fs/erofs/zmap.c:148
CPU: 0 PID: 383 Comm: syz.2.27 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/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+0x76/0xa0 kernel/entry/common.c:199
 syscall_exit_to_user_mode+0x1d/0x40 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:0x7fc6b28c6ba9
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:00007ffce83b6ef8 EFLAGS: 00000246 ORIG_RAX: 00000000000001b4
RAX: 0000000000000000 RBX: 0000000000008087 RCX: 00007fc6b28c6ba9
RDX: 0000000000000000 RSI: 000000000000001e RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000001 R09: 00000003e83b71ef
R10: 0000001b31d20000 R11: 0000000000000246 R12: 00007fc6b2b0dfac
R13: 00007fc6b2b0dfa0 R14: ffffffffffffffff R15: 0000000000000003

Crashes (10):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/14 17:53 android13-5.10-lts 911f602c2237 e2beed91 .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/07/31 10:49 android13-5.10-lts 1154f779f3f3 f8f2b4da .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/07/31 10:32 android13-5.10-lts 1154f779f3f3 f8f2b4da .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/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/09/14 17:29 android13-5.10-lts 911f602c2237 e2beed91 .config console log report syz / log [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.