syzbot


WARNING in ext4_journal_check_start

Status: upstream: reported syz repro on 2025/12/08 18:38
Reported-by: syzbot+1b8918e16f1cb8a441e1@syzkaller.appspotmail.com
First crash: 7d07h, last: 7d07h
Bug presence (1)
Date Name Commit Repro Result
2025/12/09 upstream (ToT) cb015814f8b6 syz Failed due to an error; will retry later
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 WARNING in ext4_journal_check_start -1 1 434d 434d 0/3 auto-obsoleted due to no activity on 2025/01/15 23:20
upstream WARNING in ext4_journal_check_start (2) ext4 -1 C inconclusive inconclusive 45 10d 424d 0/29 upstream: reported C repro on 2024/10/18 00:39
upstream WARNING in ext4_journal_check_start ext4 -1 syz 3 552d 600d 0/29 auto-obsoleted due to no activity on 2024/08/10 22:22

Sample crash report:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 2950 at fs/ext4/ext4_jbd2.c:73 ext4_journal_check_start+0x1eb/0x250 fs/ext4/ext4_jbd2.c:73
Modules linked in:
CPU: 0 PID: 2950 Comm: kworker/u4:11 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: writeback wb_workfn (flush-7:7)
RIP: 0010:ext4_journal_check_start+0x1eb/0x250 fs/ext4/ext4_jbd2.c:73
Code: 48 83 c4 08 41 bf e2 ff ff ff 44 89 f8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 62 d1 5b ff 41 bf fb ff ff ff eb e5 e8 55 d1 5b ff <0f> 0b eb d6 e8 4c d1 5b ff 0f 0b 43 80 7c 25 00 00 0f 85 0b ff ff
RSP: 0018:ffffc9000bd16db8 EFLAGS: 00010293
RAX: ffffffff8229bf6b RBX: ffff88805e2ee000 RCX: ffff88802b9f8000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000a8e R08: ffff88805e2e0387 R09: 1ffff1100bc5c070
R10: dffffc0000000000 R11: ffffed100bc5c071 R12: dffffc0000000000
R13: 1ffff1100bc5dcc6 R14: ffff88805e2ee630 R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc5e6a00218 CR3: 000000002665f000 CR4: 00000000003506f0
Call Trace:
 <TASK>
 __ext4_journal_start_sb+0x147/0x570 fs/ext4/ext4_jbd2.c:105
 __ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline]
 ext4_do_writepages+0xf92/0x38d0 fs/ext4/inode.c:2701
 ext4_writepages+0x1a8/0x2f0 fs/ext4/inode.c:2807
 do_writepages+0x3a2/0x600 mm/page-writeback.c:2575
 __writeback_single_inode+0x153/0xee0 fs/fs-writeback.c:1635
 writeback_sb_inodes+0x77c/0xef0 fs/fs-writeback.c:1926
 __writeback_inodes_wb+0x111/0x240 fs/fs-writeback.c:1997
 wb_writeback+0x464/0xba0 fs/fs-writeback.c:2107
 wb_check_background_flush fs/fs-writeback.c:2177 [inline]
 wb_do_writeback fs/fs-writeback.c:2265 [inline]
 wb_workfn+0xb32/0xe20 fs/fs-writeback.c:2292
 process_one_work kernel/workqueue.c:2634 [inline]
 process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
 worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
 kthread+0x2fa/0x390 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/08 18:38 linux-6.6.y 5fa4793a2d2d d6526ea3 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan WARNING in ext4_journal_check_start
* Struck through repros no longer work on HEAD.