syzbot


BUG: scheduling while atomic in jbd2_log_wait_commit

Status: premoderation: reported on 2024/04/05 01:05
Reported-by: syzbot+8f922edb0c4ee1ac431b@syzkaller.appspotmail.com
First crash: 75d, last: 6d08h

Sample crash report:
BUG: scheduling while atomic: syz-executor.0/3118/0x00000002
Modules linked in:
Preemption disabled at:
[<ffffffff81586237>] __up_write kernel/locking/rwsem.c:1428 [inline]
[<ffffffff81586237>] up_write+0x27/0x1f0 kernel/locking/rwsem.c:1682
CPU: 1 PID: 3118 Comm: syz-executor.0 Not tainted 6.1.78-syzkaller-00006-gb22d7c4ca0d3 #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/0x1b lib/dump_stack.c:113
 __schedule_bug+0x195/0x260 kernel/sched/core.c:5975
 schedule_debug kernel/sched/core.c:6002 [inline]
 __schedule+0xcf7/0x1550 kernel/sched/core.c:6637
 schedule+0xc3/0x180 kernel/sched/core.c:6820
 jbd2_log_wait_commit+0x197/0x360 fs/jbd2/journal.c:709
 __jbd2_journal_force_commit+0x163/0x1e0 fs/jbd2/journal.c:558
 jbd2_journal_force_commit_nested+0x15/0x30 fs/jbd2/journal.c:579
 ext4_should_retry_alloc+0x173/0x2d0 fs/ext4/balloc.c:709
 ext4_alloc_file_blocks+0xb72/0xcd0 fs/ext4/extents.c:4502
 ext4_fallocate+0x942/0x1e90 fs/ext4/extents.c:4758
 vfs_fallocate+0x492/0x570 fs/open.c:324
 do_vfs_ioctl+0x2150/0x29a0 fs/ioctl.c:849
 __do_sys_ioctl fs/ioctl.c:868 [inline]
 __se_sys_ioctl+0x99/0x190 fs/ioctl.c:856
 __x64_sys_ioctl+0x7b/0x90 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7faf3387cea9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007faf345b20c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007faf339b3f80 RCX: 00007faf3387cea9
RDX: 0000000020000040 RSI: 000000004030582a RDI: 0000000000000008
RBP: 00007faf338ebff4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007faf339b3f80 R15: 00007ffee09a1578
 </TASK>

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/06/13 12:22 android14-6.1 b22d7c4ca0d3 2aa5052f .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: scheduling while atomic in jbd2_log_wait_commit
2024/04/17 07:55 android14-6.1 089d1b8f6daf 18f6e127 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: scheduling while atomic in jbd2_log_wait_commit
2024/04/05 01:04 android14-6.1 ebcdb9dc211f 0ee3535e .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: scheduling while atomic in jbd2_log_wait_commit
* Struck through repros no longer work on HEAD.