[fs?] kernel BUG in end_buffer_async_write

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 38e04b3e4240 Merge tag '6.3-rc2-smb3-client-fixes' of git:..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=133fa126c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=dbab9019ad6fc418
dashboard link: https://syzkaller.appspot.com/bug?extid=e1110cf2492be8f1d060
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [bra...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ee1d0954cf7c/disk-38e04b3e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7e683e8248eb/vmlinux-38e04b3e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7a3865a0949b/bzImage-38e04b3e.xz

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

------------[ cut here ]------------
kernel BUG at fs/buffer.c:392!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.3.0-rc2-syzkaller-00077-g38e04b3e4240 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:end_buffer_async_write+0x3e4/0x4e0 fs/buffer.c:392
Code: 89 df e8 1f 99 e0 ff 48 8b 13 48 c7 c7 c0 72 f7 8a 4c 89 fe 48 c7 c1 60 6e f7 8a e8 06 a8 9e 08 e9 6a fd ff ff e8 1c e8 8a ff <0f> 0b 4c 89 e3 e8 12 e8 8a ff 48 89 df 48 c7 c6 20 72 f7 8a e8 73
RSP: 0018:ffffc90000147b60 EFLAGS: 00010246
RAX: ffffffff81ff8504 RBX: 000000000000001d RCX: ffff8880167fba80
RDX: 0000000080000100 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81ff8182 R09: ffffed10073db323
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888039ed9910 R14: 0000000000000001 R15: 1ffff110073db322
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3222c000 CR3: 0000000029b91000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
end_bio_bh_io_sync+0xb7/0x110 fs/buffer.c:2703
req_bio_endio block/blk-mq.c:795 [inline]
blk_update_request+0x4d7/0xfe0 block/blk-mq.c:927
blk_mq_end_request+0x3e/0x70 block/blk-mq.c:1054
blk_complete_reqs block/blk-mq.c:1132 [inline]
blk_done_softirq+0xfc/0x150 block/blk-mq.c:1137
__do_softirq+0x2ab/0x908 kernel/softirq.c:571
run_ksoftirqd+0xc5/0x120 kernel/softirq.c:934
smpboot_thread_fn+0x533/0x9f0 kernel/smpboot.c:164
kthread+0x270/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:end_buffer_async_write+0x3e4/0x4e0 fs/buffer.c:392
Code: 89 df e8 1f 99 e0 ff 48 8b 13 48 c7 c7 c0 72 f7 8a 4c 89 fe 48 c7 c1 60 6e f7 8a e8 06 a8 9e 08 e9 6a fd ff ff e8 1c e8 8a ff <0f> 0b 4c 89 e3 e8 12 e8 8a ff 48 89 df 48 c7 c6 20 72 f7 8a e8 73
RSP: 0018:ffffc90000147b60 EFLAGS: 00010246

RAX: ffffffff81ff8504 RBX: 000000000000001d RCX: ffff8880167fba80
RDX: 0000000080000100 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff81ff8182 R09: ffffed10073db323
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff888039ed9910 R14: 0000000000000001 R15: 1ffff110073db322
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b3222c000 CR3: 0000000029b91000 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 syzk...@googlegroups.com.

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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 51f269a6ecc7 Merge tag 'probes-fixes-6.4-rc4' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15ed0e7d280000
kernel config: https://syzkaller.appspot.com/x/.config?x=3da6c5d3e0a6c932
dashboard link: https://syzkaller.appspot.com/bug?extid=e1110cf2492be8f1d060
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1336c6b5280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12c0a5a5280000
CC: [bra...@kernel.org konishi...@gmail.com linux-...@vger.kernel.org linux-...@vger.kernel.org linux...@vger.kernel.org vi...@zeniv.linux.org.uk]

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8a8c8e41a6b0/disk-51f269a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ffc3737b4233/vmlinux-51f269a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d49888e5beb1/bzImage-51f269a6.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/99d35f050c12/mount_0.gz

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

------------[ cut here ]------------

kernel BUG at fs/buffer.c:391!

invalid opcode: 0000 [#1] PREEMPT SMP KASAN

CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.4.0-rc4-syzkaller-00268-g51f269a6ecc7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:end_buffer_async_write+0x2db/0x340 fs/buffer.c:391
Code: 65 00 fe 4c 89 ff e8 d4 a3 ff ff be 08 00 00 00 48 89 c7 48 89 c3 e8 b4 31 e0 ff f0 80 4b 01 01 e9 07 fe ff ff e8 45 62 8d ff <0f> 0b e8 3e 62 8d ff 0f 0b 48 89 df e8 34 2b e0 ff e9 d9 fe ff ff
RSP: 0018:ffffc90000147c98 EFLAGS: 00010246

RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000100
RDX: ffff88801664bb80 RSI: ffffffff81f6e3fb RDI: 0000000000000001
RBP: ffff88806fbde570 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: ffffffff81f6e120 R14: ffff88801e24ee00 R15: ffff88802a45a788

FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f42b45b0000 CR3: 000000007b04a000 CR4: 0000000000350ef0
Call Trace:
<TASK>
end_bio_bh_io_sync+0xde/0x130 fs/buffer.c:2730
bio_endio+0x5af/0x6c0 block/bio.c:1608
req_bio_endio block/blk-mq.c:761 [inline]
blk_update_request+0x5c5/0x1620 block/blk-mq.c:906
blk_mq_end_request+0x59/0x4c0 block/blk-mq.c:1023
lo_complete_rq+0x1c6/0x280 drivers/block/loop.c:370
blk_complete_reqs+0xad/0xe0 block/blk-mq.c:1101
__do_softirq+0x1d4/0x905 kernel/softirq.c:571
run_ksoftirqd kernel/softirq.c:939 [inline]
run_ksoftirqd+0x31/0x60 kernel/softirq.c:931
smpboot_thread_fn+0x659/0x9e0 kernel/smpboot.c:164
kthread+0x344/0x440 kernel/kthread.c:379

ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---

RIP: 0010:end_buffer_async_write+0x2db/0x340 fs/buffer.c:391
Code: 65 00 fe 4c 89 ff e8 d4 a3 ff ff be 08 00 00 00 48 89 c7 48 89 c3 e8 b4 31 e0 ff f0 80 4b 01 01 e9 07 fe ff ff e8 45 62 8d ff <0f> 0b e8 3e 62 8d ff 0f 0b 48 89 df e8 34 2b e0 ff e9 d9 fe ff ff
RSP: 0018:ffffc90000147c98 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000100
RDX: ffff88801664bb80 RSI: ffffffff81f6e3fb RDI: 0000000000000001
RBP: ffff88806fbde570 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: ffffffff81f6e120 R14: ffff88801e24ee00 R15: ffff88802a45a788

FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f42b45b0000 CR3: 000000007b04a000 CR4: 0000000000350ef0


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

[syzbot]

Sending this report to the next reporting stage.