[v5.15] WARNING in btrfs_truncate_inode_items (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: aabd761612db Linux 5.15.215
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11074549580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f161cbc9aef65db0
dashboard link: https://syzkaller.appspot.com/bug?extid=d8f38c2c6a69a4331a43
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f636f56d3662/disk-aabd7616.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f1a46620f40c/vmlinux-aabd7616.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9b78bb48b022/bzImage-aabd7616.xz

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

R10: 0001000000201005 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f88b8291128 R14: 00007f88b8291090 R15: 00007ffe12930bc8
</TASK>
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4385 at fs/btrfs/inode.c:5021 btrfs_truncate_inode_items+0x1e6e/0x21e0 fs/btrfs/inode.c:5021
Modules linked in:
CPU: 1 PID: 4385 Comm: syz.4.5 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:btrfs_truncate_inode_items+0x1e6e/0x21e0 fs/btrfs/inode.c:5021
Code: 06 e9 b0 fb ff ff e8 e1 82 2e fe 0f 1f 44 00 00 e8 d7 82 2e fe eb 15 e8 d0 82 2e fe 48 c7 c7 c0 78 6b 8a 89 de e8 e2 af 6a 06 <0f> 0b 48 8b 7c 24 20 48 c7 c6 60 7d 6b 8a ba 9d 13 00 00 89 d9 e8
RSP: 0018:ffffc900039cf3e0 EFLAGS: 00010246
RAX: 98d3a5de2e908200 RBX: 00000000fffffff4 RCX: ffff88802a6f9dc0
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900039cf6b0 R08: ffff8880b912795b R09: 1ffff11017224f2b
R10: dffffc0000000000 R11: ffffed1017224f2c R12: 1ffff1100e1a19c3
R13: dffffc0000000000 R14: dffffc0000000000 R15: ffff888070d0ce18
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc428479458 CR3: 000000002ad7f000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_evict_inode+0xb5b/0xf90 fs/btrfs/inode.c:5726
evict+0x4b6/0x8b0 fs/inode.c:647
__dentry_kill+0x412/0x630 fs/dcache.c:586
dentry_kill+0xb8/0x290 fs/dcache.c:-1
dput+0xd8/0x1a0 fs/dcache.c:893
__fput+0x5a5/0x8c0 fs/file_table.c:319
task_work_run+0x125/0x1a0 kernel/task_work.c:188
exit_task_work include/linux/task_work.h:33 [inline]
do_exit+0x635/0x2110 kernel/exit.c:890
do_group_exit+0x12c/0x2f0 kernel/exit.c:1004
get_signal+0x7eb/0x12e0 kernel/signal.c:2909
arch_do_signal_or_restart+0xe6/0x12a0 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:154 [inline]
exit_to_user_mode_loop+0x9e/0x130 kernel/entry/common.c:178
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f88b80090d9
Code: Unable to access opcode bytes at RIP 0x7f88b80090af.
RSP: 002b:00007f88b6240028 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: 00000000001d0000 RBX: 00007f88b8291090 RCX: 00007f88b80090d9
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 0000000000000009
RBP: 00007f88b80a0024 R08: 0000000000000000 R09: 0000000000000000
R10: 0001000000201005 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f88b8291128 R14: 00007f88b8291090 R15: 00007ffe12930bc8
</TASK>


---
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