syzbot


BUG: scheduling while atomic in kjournald2

Status: premoderation: reported on 2024/04/03 16:44
Reported-by: syzbot+140ebb9135abd96a0d20@syzkaller.appspotmail.com
First crash: 110d, last: 59d

Sample crash report:
BUG: scheduling while atomic: jbd2/sda1-8/64/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81ea370a>] spin_trylock include/linux/spinlock.h:373 [inline]
[<ffffffff81ea370a>] ext4_lock_group fs/ext4/ext4.h:3497 [inline]
[<ffffffff81ea370a>] ext4_free_data_in_buddy fs/ext4/mballoc.c:3688 [inline]
[<ffffffff81ea370a>] ext4_process_freed_data+0x5ea/0xf40 fs/ext4/mballoc.c:3742
CPU: 0 PID: 64 Comm: jbd2/sda1-8 Tainted: G        W         5.15.149-syzkaller-00055-g424f92bcbe8f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/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
 kjournald2+0x4e9/0x890 fs/jbd2/journal.c:249
 kthread+0x421/0x510 kernel/kthread.c:337
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/05/24 21:32 android13-5.15-lts 424f92bcbe8f a10a183e .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15 BUG: scheduling while atomic in kjournald2
2024/04/03 16:43 android13-5.15-lts 993bed180178 51c4dcff .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-15-perf BUG: scheduling while atomic in kjournald2
* Struck through repros no longer work on HEAD.