[v5.15] kernel BUG in btrfs_run_defrag_inodes

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 14e468424d3e Linux 5.15.166
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13662d63980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8d58a8e8a6c2ab88
dashboard link: https://syzkaller.appspot.com/bug?extid=71f30e7212f366d70e5e
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/c745bbe4ebd8/disk-14e46842.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f07c263e8276/vmlinux-14e46842.xz
kernel image: https://storage.googleapis.com/syzbot-assets/511d53dfa858/bzImage-14e46842.xz

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

------------[ cut here ]------------
kernel BUG at fs/inode.c:1756!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4607 Comm: btrfs-cleaner Not tainted 5.15.166-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:iput+0x8aa/0x8b0 fs/inode.c:1756
Code: ed ff e9 0b fc ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c c6 fe ff ff 4c 89 f7 e8 20 67 ed ff e9 b9 fe ff ff e8 46 9e a3 ff <0f> 0b 0f 1f 40 00 55 41 57 41 56 41 55 41 54 53 41 89 ce 41 89 d7
RSP: 0018:ffffc90002fc7c98 EFLAGS: 00010293
RAX: ffffffff81dcbbba RBX: 0000000000000040 RCX: ffff888021f9bb80
RDX: 0000000000000000 RSI: 0000000000000040 RDI: 0000000000000000
RBP: ffff888073f2bfa0 R08: ffffffff81dcb36b R09: fffffbfff19e6395
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888073f2c078
R13: ffff88806730b000 R14: 0000000000000000 R15: 0000000000000005
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c2dcd06 CR3: 0000000061ac3000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__btrfs_run_defrag_inode fs/btrfs/file.c:329 [inline]
btrfs_run_defrag_inodes+0xad6/0xd50 fs/btrfs/file.c:372
cleaner_kthread+0x205/0x390 fs/btrfs/disk-io.c:1829
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace 002e4cee63bd0ac7 ]---
RIP: 0010:iput+0x8aa/0x8b0 fs/inode.c:1756
Code: ed ff e9 0b fc ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c c6 fe ff ff 4c 89 f7 e8 20 67 ed ff e9 b9 fe ff ff e8 46 9e a3 ff <0f> 0b 0f 1f 40 00 55 41 57 41 56 41 55 41 54 53 41 89 ce 41 89 d7
RSP: 0018:ffffc90002fc7c98 EFLAGS: 00010293
RAX: ffffffff81dcbbba RBX: 0000000000000040 RCX: ffff888021f9bb80
RDX: 0000000000000000 RSI: 0000000000000040 RDI: 0000000000000000
RBP: ffff888073f2bfa0 R08: ffffffff81dcb36b R09: fffffbfff19e6395
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888073f2c078
R13: ffff88806730b000 R14: 0000000000000000 R15: 0000000000000005
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2c71aff8 CR3: 0000000020103000 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.

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