[syzbot] [ext4?] kernel BUG in ext4_mb_use_inode_pa (2)

[syzbot <syzbot+d79019213609e7056a19@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    defaf1a2113a Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=145fe1c9980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=8da8b059e43c5370
dashboard link: https://syzkaller.appspot.com/bug?extid=d79019213609e7056a19
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/af289143b46d/disk-defaf1a2.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/194e789e9f9f/vmlinux-defaf1a2.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e00d8590048d/bzImage-defaf1a2.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d79019213609e7056a19@syzkaller.appspotmail.com

EXT4-fs (sda1): Delayed block allocation failed for inode 1940 at logical offset 1516 with max blocks 20 with error 117
EXT4-fs (sda1): This should not happen!! Data will be lost
------------[ cut here ]------------
kernel BUG at fs/ext4/mballoc.c:4689!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 UID: 0 PID: 5797 Comm: kworker/u8:16 Not tainted 6.11.0-rc1-syzkaller-00293-gdefaf1a2113a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
Workqueue: writeback wb_workfn (flush-8:0)
RIP: 0010:ext4_mb_use_inode_pa+0x4cf/0x5d0 fs/ext4/mballoc.c:4689
Code: 00 48 83 c4 30 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc e8 d2 91 43 ff 90 0f 0b e8 ca 91 43 ff 90 0f 0b e8 c2 91 43 ff 90 <0f> 0b e8 ba 91 43 ff 90 0f 0b e8 22 b9 a0 ff e9 11 fe ff ff 48 89
RSP: 0018:ffffc9000358eb88 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88806a511360 RCX: ffffffff8246e8ee
RDX: ffff888052c88000 RSI: ffffffff8246e96e RDI: 0000000000000004
RBP: ffff88806a419740 R08: 0000000000000004 R09: 0000000000000002
R10: 000000000000002c R11: 0000000000000000 R12: 0000000000000002
R13: 000000000000002c R14: 0000000000023800 R15: 0000000000023600
FS:  0000000000000000(0000) GS:ffff8880b9200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b301feff8 CR3: 000000006908c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ext4_mb_use_preallocated.constprop.0+0xeff/0x1520 fs/ext4/mballoc.c:4906
 ext4_mb_new_blocks+0x9b3/0x4e40 fs/ext4/mballoc.c:6210
 ext4_ext_map_blocks+0x1c24/0x5cd0 fs/ext4/extents.c:4318
 ext4_map_blocks+0x61d/0x17d0 fs/ext4/inode.c:652
 mpage_map_one_extent fs/ext4/inode.c:2237 [inline]
 mpage_map_and_submit_extent fs/ext4/inode.c:2290 [inline]
 ext4_do_writepages+0x172c/0x3250 fs/ext4/inode.c:2753
 ext4_writepages+0x303/0x730 fs/ext4/inode.c:2842
 do_writepages+0x1a3/0x7f0 mm/page-writeback.c:2683
 __writeback_single_inode+0x163/0xf90 fs/fs-writeback.c:1651
 writeback_sb_inodes+0x611/0x1150 fs/fs-writeback.c:1947
 __writeback_inodes_wb+0xff/0x2e0 fs/fs-writeback.c:2018
 wb_writeback+0x721/0xb50 fs/fs-writeback.c:2129
 wb_check_start_all fs/fs-writeback.c:2255 [inline]
 wb_do_writeback fs/fs-writeback.c:2281 [inline]
 wb_workfn+0x9fb/0xf40 fs/fs-writeback.c:2314
 process_one_work+0x9c5/0x1b40 kernel/workqueue.c:3231
 process_scheduled_works kernel/workqueue.c:3312 [inline]
 worker_thread+0x6c8/0xf20 kernel/workqueue.c:3390
 kthread+0x2c1/0x3a0 kernel/kthread.c:389
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ext4_mb_use_inode_pa+0x4cf/0x5d0 fs/ext4/mballoc.c:4689
Code: 00 48 83 c4 30 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc e8 d2 91 43 ff 90 0f 0b e8 ca 91 43 ff 90 0f 0b e8 c2 91 43 ff 90 <0f> 0b e8 ba 91 43 ff 90 0f 0b e8 22 b9 a0 ff e9 11 fe ff ff 48 89
RSP: 0018:ffffc9000358eb88 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff88806a511360 RCX: ffffffff8246e8ee
RDX: ffff888052c88000 RSI: ffffffff8246e96e RDI: 0000000000000004
RBP: ffff88806a419740 R08: 0000000000000004 R09: 0000000000000002
R10: 000000000000002c R11: 0000000000000000 R12: 0000000000000002
R13: 000000000000002c R14: 0000000000023800 R15: 0000000000023600
FS:  0000000000000000(0000) GS:ffff8880b9200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b301feff8 CR3: 000000006908c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup