BUG: scheduling while atomic in f2fs_register_inmem_page (2)

Status: upstream: reported C repro on 2026/11/07 21:12
Reported-by: syzbot+8347ca8355b5e9e8126c@syzkaller.appspotmail.com
First crash: 1d09h, last: 15h38m
▶ ▼ Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-54 BUG: scheduling while atomic in f2fs_register_inmem_page 5 1 1311d 1311d 0/2 closed as invalid on 2023/05/12 10:24
android-5-15 BUG: scheduling while atomic in f2fs_register_inmem_page origin:lts 5 syz, C error done 4 1079d 1334d 0/2 auto-obsoleted due to no activity on 2024/03/04 10:27
android-5-10 BUG: scheduling while atomic in f2fs_register_inmem_page 5 syz, C error inconclusive 1 1334d 1334d 0/2 closed as invalid on 2023/05/12 10:22

Sample crash report:
BUG: scheduling while atomic: syz-executor203/372/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81952eb4>] spin_lock include/linux/spinlock.h:355 [inline]
[<ffffffff81952eb4>] zap_pte_range mm/memory.c:1272 [inline]
[<ffffffff81952eb4>] zap_pmd_range mm/memory.c:1435 [inline]
[<ffffffff81952eb4>] zap_pud_range mm/memory.c:1464 [inline]
[<ffffffff81952eb4>] zap_p4d_range mm/memory.c:1485 [inline]
[<ffffffff81952eb4>] unmap_page_range+0xa54/0x2190 mm/memory.c:1506
CPU: 0 PID: 372 Comm: syz-executor203 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/15/2026
Call Trace:
 __dump_stack+0x21/0x24 lib/dump_stack.c:77
 dump_stack_lvl+0x1a7/0x208 lib/dump_stack.c:118
 dump_stack+0x15/0x1c lib/dump_stack.c:135
 __schedule_bug+0x183/0x240 kernel/sched/core.c:4545
 schedule_debug kernel/sched/core.c:4572 [inline]
 __schedule+0xcee/0x13e0 kernel/sched/core.c:4700
 schedule+0x13c/0x1d0 kernel/sched/core.c:4884
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:4943
 __mutex_lock_common kernel/locking/mutex.c:1053 [inline]
 __mutex_lock+0x5d4/0xc40 kernel/locking/mutex.c:1117
 __mutex_lock_slowpath+0xe/0x10 kernel/locking/mutex.c:1379
 mutex_lock+0xdb/0xf0 kernel/locking/mutex.c:299
 f2fs_register_inmem_page+0x211/0x470 fs/f2fs/segment.c:202
 f2fs_set_data_page_dirty+0x557/0x6e0 fs/f2fs/data.c:3648
 set_page_dirty+0x1a2/0x300 mm/page-writeback.c:2608
 zap_pte_range mm/memory.c:1308 [inline]
 zap_pmd_range mm/memory.c:1435 [inline]
 zap_pud_range mm/memory.c:1464 [inline]
 zap_p4d_range mm/memory.c:1485 [inline]
 unmap_page_range+0x104c/0x2190 mm/memory.c:1506
 unmap_single_vma mm/memory.c:1551 [inline]
 unmap_vmas+0x25f/0x360 mm/memory.c:1583
 exit_mmap+0x309/0x590 mm/mmap.c:3385
 __mmput+0x92/0x2d0 kernel/fork.c:1153
 mmput+0x4e/0x150 kernel/fork.c:1176
 exit_mm kernel/exit.c:546 [inline]
 do_exit+0x9d8/0x24e0 kernel/exit.c:866
 do_group_exit+0x149/0x310 kernel/exit.c:993
 get_signal+0xfb1/0x1300 kernel/signal.c:2806
 arch_do_signal_or_restart+0xe7/0x11b0 arch/x86/kernel/signal.c:805
 handle_signal_work kernel/entry/common.c:148 [inline]
 exit_to_user_mode_loop+0xa2/0xe0 kernel/entry/common.c:172
 exit_to_user_mode_prepare+0x76/0xa0 kernel/entry/common.c:202
 syscall_exit_to_user_mode+0x1d/0x40 kernel/entry/common.c:277
 do_syscall_64+0x3d/0x40 arch/x86/entry/common.c:56
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fb35341cb89
Code: Unable to access opcode bytes at RIP 0x7fb35341cb5f.
RSP: 002b:00007fb3533d0218 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: 0000000000c21000 RBX: 00007fb3534c9e58 RCX: 00007fb35341cb89
RDX: 00000000fffffeb1 RSI: 0000200000005d80 RDI: 0000000000000006
RBP: 00007fb3534c9e50 R08: 00007fb3533d06c0 R09: 33203a6b63617473
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fb35349aabc
R13: 0000200000000000 R14: 0000200000005d80 R15: 00000000fffffeb1
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(val > preempt_count())
WARNING: CPU: 0 PID: 372 at kernel/sched/core.c:4488 preempt_count_sub+0xa7/0x170 kernel/sched/core.c:4488
Modules linked in:
CPU: 0 PID: 372 Comm: syz-executor203 Tainted: G        W         syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/15/2026
RIP: 0010:preempt_count_sub+0xa7/0x170 kernel/sched/core.c:4488
Code: e8 03 0f b6 04 18 84 c0 0f 85 8b 00 00 00 83 3d b6 e1 7e 05 00 75 d2 48 c7 c7 80 14 e8 84 48 c7 c6 20 15 e8 84 e8 19 68 35 03 <0f> 0b eb bb e8 50 9d f6 00 85 c0 74 b2 48 c7 c0 c8 b3 c3 86 48 c1
RSP: 0018:ffffc90000fe7588 EFLAGS: 00010246
RAX: 32e1e7670dcf3f00 RBX: dffffc0000000000 RCX: ffff88810c5b5000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90000fe7598 R08: ffff8881f7127493 R09: 1ffff1103ee24e92
R10: dffffc0000000000 R11: ffffed103ee24e93 R12: 1ffff920001fcee0
R13: dffffc0000000000 R14: ffff88811df135f0 R15: 1ffff920001fcf24
FS:  0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000852000 CR3: 0000000105f96000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 __raw_spin_unlock include/linux/spinlock_api_smp.h:152 [inline]
 _raw_spin_unlock+0x4d/0x70 kernel/locking/spinlock.c:183
 spin_unlock include/linux/spinlock.h:395 [inline]
 zap_pte_range mm/memory.c:1375 [inline]
 zap_pmd_range mm/memory.c:1435 [inline]
 zap_pud_range mm/memory.c:1464 [inline]
 zap_p4d_range mm/memory.c:1485 [inline]
 unmap_page_range+0x1d78/0x2190 mm/memory.c:1506
 unmap_single_vma mm/memory.c:1551 [inline]
 unmap_vmas+0x25f/0x360 mm/memory.c:1583
 exit_mmap+0x309/0x590 mm/mmap.c:3385
 __mmput+0x92/0x2d0 kernel/fork.c:1153
 mmput+0x4e/0x150 kernel/fork.c:1176
 exit_mm kernel/exit.c:546 [inline]
 do_exit+0x9d8/0x24e0 kernel/exit.c:866
 do_group_exit+0x149/0x310 kernel/exit.c:993
 get_signal+0xfb1/0x1300 kernel/signal.c:2806
 arch_do_signal_or_restart+0xe7/0x11b0 arch/x86/kernel/signal.c:805
 handle_signal_work kernel/entry/common.c:148 [inline]
 exit_to_user_mode_loop+0xa2/0xe0 kernel/entry/common.c:172
 exit_to_user_mode_prepare+0x76/0xa0 kernel/entry/common.c:202
 syscall_exit_to_user_mode+0x1d/0x40 kernel/entry/common.c:277
 do_syscall_64+0x3d/0x40 arch/x86/entry/common.c:56
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fb35341cb89
Code: Unable to access opcode bytes at RIP 0x7fb35341cb5f.
RSP: 002b:00007fb3533d0218 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: 0000000000c21000 RBX: 00007fb3534c9e58 RCX: 00007fb35341cb89
RDX: 00000000fffffeb1 RSI: 0000200000005d80 RDI: 0000000000000006
RBP: 00007fb3534c9e50 R08: 00007fb3533d06c0 R09: 33203a6b63617473
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fb35349aabc
R13: 0000200000000000 R14: 0000200000005d80 R15: 00000000fffffeb1
---[ end trace e5df8cc5846ff082 ]---

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/07 21:45 android13-5.10-lts f61a392235e0 5cecaf1f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 BUG: scheduling while atomic in f2fs_register_inmem_page
2026/11/07 21:07 android13-5.10-lts f61a392235e0 5cecaf1f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 BUG: scheduling while atomic in f2fs_register_inmem_page
2026/11/08 14:27 android13-5.10-lts f61a392235e0 5cecaf1f .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 BUG: scheduling while atomic in f2fs_register_inmem_page
2026/11/07 22:48 android13-5.10-lts f61a392235e0 5cecaf1f .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 BUG: scheduling while atomic in f2fs_register_inmem_page
2026/11/07 20:37 android13-5.10-lts f61a392235e0 5cecaf1f .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 BUG: scheduling while atomic in f2fs_register_inmem_page
* Struck through repros no longer work on HEAD.