[v5.15] WARNING in ext4_put_io_end_defer

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9465fef4ae35 Linux 5.15.153
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=112977ad180000
kernel config: https://syzkaller.appspot.com/x/.config?x=176c746ee3348b33
dashboard link: https://syzkaller.appspot.com/bug?extid=c441538a83a006b4939a
compiler: Debian clang version 15.0.6, 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/2962c02652ce/disk-9465fef4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d0f5a1ce082d/vmlinux-9465fef4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/86b5b1eea636/bzImage-9465fef4.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 0 at fs/ext4/page-io.c:231 ext4_put_io_end_defer+0x2d5/0x300 fs/ext4/page-io.c:297
Modules linked in:
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.153-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:ext4_add_complete_io fs/ext4/page-io.c:231 [inline]
RIP: 0010:ext4_put_io_end_defer+0x2d5/0x300 fs/ext4/page-io.c:297
Code: 65 00 eb 05 e8 4c c7 5b ff 48 8b 3c 24 48 8b 74 24 08 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d e9 c0 02 01 08 e8 2b c7 5b ff <0f> 0b e9 b7 fe ff ff 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c 85 fd ff
RSP: 0018:ffffc90000dd0ad8 EFLAGS: 00010246
RAX: ffffffff82247285 RBX: ffff888020e50378 RCX: ffff88813fe78000
RDX: 0000000000000101 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff88805e6834a0 R08: ffffffff82247030 R09: ffffed100b500dc2
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88805a806de0
R13: ffff888020e50000 R14: ffff88805e683478 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f91b34f0988 CR3: 00000000640bc000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
ext4_end_bio+0x357/0x5b0 fs/ext4/page-io.c:360
req_bio_endio block/blk-core.c:261 [inline]
blk_update_request+0x87c/0x1470 block/blk-core.c:1441
scsi_end_request+0x83/0x980 drivers/scsi/scsi_lib.c:544
scsi_io_completion+0x1fa/0x540 drivers/scsi/scsi_lib.c:940
blk_complete_reqs block/blk-mq.c:587 [inline]
blk_done_softirq+0xf2/0x130 block/blk-mq.c:592
__do_softirq+0x3b3/0x93a kernel/softirq.c:558
invoke_softirq kernel/softirq.c:432 [inline]
__irq_exit_rcu+0x155/0x240 kernel/softirq.c:637
irq_exit_rcu+0x5/0x20 kernel/softirq.c:649
common_interrupt+0xa4/0xc0 arch/x86/kernel/irq.c:240
</IRQ>
<TASK>
asm_common_interrupt+0x22/0x40 arch/x86/include/asm/idtentry.h:629
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:22 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:132 [inline]
RIP: 0010:acpi_safe_halt drivers/acpi/processor_idle.c:110 [inline]
RIP: 0010:acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:570
Code: d0 5a f7 48 83 e3 08 0f 85 0a 01 00 00 4c 8d 74 24 20 e8 d4 4a 61 f7 0f 1f 44 00 00 e8 ea cc 5a f7 0f 00 2d f3 49 bd 00 fb f4 <4c> 89 f3 48 c1 eb 03 42 80 3c 3b 00 74 08 4c 89 f7 e8 3b 8c a4 f7
RSP: 0018:ffffc90000d67b00 EFLAGS: 000002d3
RAX: ffffffff8a256cc6 RBX: 0000000000000000 RCX: ffff88813fe78000
RDX: 0000000000000000 RSI: ffffffff8a8b1500 RDI: ffffffff8ad88fc0
RBP: ffffc90000d67b90 R08: ffffffff8186b7c0 R09: ffffed1027fcf001
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff920001acf60
R13: ffff888012dd7004 R14: ffffc90000d67b20 R15: dffffc0000000000
acpi_idle_enter+0x352/0x4f0 drivers/acpi/processor_idle.c:705
cpuidle_enter_state+0x521/0xef0 drivers/cpuidle/cpuidle.c:237
cpuidle_enter+0x59/0x90 drivers/cpuidle/cpuidle.c:351
call_cpuidle kernel/sched/idle.c:158 [inline]
cpuidle_idle_call kernel/sched/idle.c:239 [inline]
do_idle+0x3e4/0x670 kernel/sched/idle.c:306
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:403
start_secondary+0x371/0x500 arch/x86/kernel/smpboot.c:281
secondary_startup_64_no_verify+0xb1/0xbb
</TASK>
----------------
Code disassembly (best guess):
0: d0 5a f7 rcrb -0x9(%rdx)
3: 48 83 e3 08 and $0x8,%rbx
7: 0f 85 0a 01 00 00 jne 0x117
d: 4c 8d 74 24 20 lea 0x20(%rsp),%r14
12: e8 d4 4a 61 f7 call 0xf7614aeb
17: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1)
1c: e8 ea cc 5a f7 call 0xf75acd0b
21: 0f 00 2d f3 49 bd 00 verw 0xbd49f3(%rip) # 0xbd4a1b
28: fb sti
29: f4 hlt
* 2a: 4c 89 f3 mov %r14,%rbx <-- trapping instruction
2d: 48 c1 eb 03 shr $0x3,%rbx
31: 42 80 3c 3b 00 cmpb $0x0,(%rbx,%r15,1)
36: 74 08 je 0x40
38: 4c 89 f7 mov %r14,%rdi
3b: e8 3b 8c a4 f7 call 0xf7a48c7b


---
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 syzk...@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