syzbot


WARNING in ext4_journal_check_start

Status: upstream: reported on 2024/10/07 23:20
Reported-by: syzbot+63dee419b0f3b408c5f4@syzkaller.appspotmail.com
First crash: 10d, last: 10d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING in ext4_journal_check_start (2) ext4 C 2 12h17m 4h42m 0/28 upstream: reported C repro on 2024/10/18 00:39
upstream WARNING in ext4_journal_check_start ext4 syz 3 128d 176d 0/28 auto-obsoleted due to no activity on 2024/08/10 22:22

Sample crash report:
EXT4-fs (loop1): i_reserved_data_blocks=132
EXT4-fs (loop1): Delayed block allocation failed for inode 18 at logical offset 2052 with max blocks 52 with error 28
------------[ cut here ]------------
WARNING: CPU: 1 PID: 144 at fs/ext4/ext4_jbd2.c:75 ext4_journal_check_start+0x1e5/0x240
Modules linked in:
CPU: 1 PID: 144 Comm: kworker/u4:1 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: writeback wb_workfn (flush-7:1)
RIP: 0010:ext4_journal_check_start+0x1e5/0x240 fs/ext4/ext4_jbd2.c:75
Code: 11 18 15 00 48 83 c4 08 bb e2 ff ff ff 89 d8 5b 41 5c 41 5d 41 5e 41 5f c3 e8 b7 28 6b ff bb fb ff ff ff eb e8 e8 ab 28 6b ff <0f> 0b 43 80 7c 25 00 00 0f 85 18 ff ff ff e9 1b ff ff ff 89 d9 80
RSP: 0018:ffffc9000141ee48 EFLAGS: 00010293
RAX: ffffffff821531c5 RBX: 0000000000000004 RCX: ffff888018199dc0
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000004
RBP: 0000000000000001 R08: ffffffff821530d5 R09: ffffed100d0bd071
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff1100fcda8cf R14: ffff88807e6d4000 R15: ffff88807e6d4678
FS:  0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fa02d07bf98 CR3: 000000002a1de000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 __ext4_journal_start_sb+0xbe/0x370 fs/ext4/ext4_jbd2.c:98
 __ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline]
 ext4_writepages+0x114f/0x3d10 fs/ext4/inode.c:2811
 do_writepages+0x481/0x730 mm/page-writeback.c:2386
 __writeback_single_inode+0x15b/0xe30 fs/fs-writeback.c:1647
 writeback_sb_inodes+0xbce/0x1a40 fs/fs-writeback.c:1930
 __writeback_inodes_wb+0x114/0x400 fs/fs-writeback.c:2001
 wb_writeback+0x465/0xc50 fs/fs-writeback.c:2106
 wb_check_background_flush fs/fs-writeback.c:2172 [inline]
 wb_do_writeback fs/fs-writeback.c:2260 [inline]
 wb_workfn+0xd07/0x1130 fs/fs-writeback.c:2288
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
 kthread+0x3f6/0x4f0 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/10/07 23:19 linux-5.15.y 3a5928702e71 d7906eff .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan WARNING in ext4_journal_check_start
* Struck through repros no longer work on HEAD.