[syzbot] [btrfs?] WARNING in __btrfs_update_delayed_inode (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9551a26f17d9 Merge tag 'loongarch-6.19' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=141f31b4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f315601b98a91c0b
dashboard link: https://syzkaller.appspot.com/bug?extid=d85308bac7187ac131d3
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b23c812ec291/disk-9551a26f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8b0564ab1672/vmlinux-9551a26f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b8aac5f6fcdb/bzImage-9551a26f.xz

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

------------[ cut here ]------------
BTRFS: Transaction aborted (error -28)
WARNING: fs/btrfs/delayed-inode.c:1039 at 0x0, CPU#1: syz.1.67/6479
Modules linked in:
CPU: 1 UID: 0 PID: 6479 Comm: syz.1.67 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:__btrfs_update_delayed_inode+0xcc6/0xed0 fs/btrfs/delayed-inode.c:1039
Code: d1 e1 fd e9 22 01 00 00 e8 57 aa c7 fd 84 c0 74 23 e8 8e d1 e1 fd e9 0f 01 00 00 e8 84 d1 e1 fd 48 8d 3d 5d 2d 05 0b 44 89 ee <67> 48 0f b9 3a e9 2c 01 00 00 e8 3b 97 f4 06 89 c3 31 ff 89 c6 e8
RSP: 0018:ffffc9000daf7080 EFLAGS: 00010283
RAX: ffffffff83dea0bc RBX: 00000000ffffffe4 RCX: 0000000000080000
RDX: ffffc9000d259000 RSI: 00000000ffffffe4 RDI: ffffffff8ee3ce20
RBP: ffffc9000daf7190 R08: ffff888028a01e40 R09: 0000000000000003
R10: 0000000000000100 R11: 00000000fffffffb R12: ffff88805e9ad9b0
R13: 00000000ffffffe4 R14: ffff88803dd5d580 R15: 0000000000000000
FS: 00007f393a8ee6c0(0000) GS:ffff888126e06000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f87afed8000 CR3: 000000003a514000 CR4: 00000000003526f0
Call Trace:
<TASK>
btrfs_update_delayed_inode fs/btrfs/delayed-inode.c:1115 [inline]
__btrfs_commit_inode_delayed_items+0x1cfc/0x1e70 fs/btrfs/delayed-inode.c:1138
__btrfs_run_delayed_items+0x215/0x540 fs/btrfs/delayed-inode.c:1173
btrfs_commit_transaction+0x8cb/0x3b10 fs/btrfs/transaction.c:2343
prepare_to_relocate+0x3a1/0x490 fs/btrfs/relocation.c:3479
relocate_block_group+0x132/0xd70 fs/btrfs/relocation.c:3504
btrfs_relocate_block_group+0x580/0xba0 fs/btrfs/relocation.c:3966
btrfs_relocate_chunk+0x12f/0x5d0 fs/btrfs/volumes.c:3424
__btrfs_balance+0x190e/0x24f0 fs/btrfs/volumes.c:4197
btrfs_balance+0xac2/0x11b0 fs/btrfs/volumes.c:4571
btrfs_ioctl_balance+0x3d6/0x610 fs/btrfs/ioctl.c:3525
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:597 [inline]
__se_sys_ioctl+0xff/0x170 fs/ioctl.c:583
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f393c68f749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f393a8ee038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f393c8e5fa0 RCX: 00007f393c68f749
RDX: 0000200000000180 RSI: 00000000c4009420 RDI: 0000000000000004
RBP: 00007f393c713f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f393c8e6038 R14: 00007f393c8e5fa0 R15: 00007ffd84049f78
</TASK>
----------------
Code disassembly (best guess):
0: d1 e1 shl %ecx
2: fd std
3: e9 22 01 00 00 jmp 0x12a
8: e8 57 aa c7 fd call 0xfdc7aa64
d: 84 c0 test %al,%al
f: 74 23 je 0x34
11: e8 8e d1 e1 fd call 0xfde1d1a4
16: e9 0f 01 00 00 jmp 0x12a
1b: e8 84 d1 e1 fd call 0xfde1d1a4
20: 48 8d 3d 5d 2d 05 0b lea 0xb052d5d(%rip),%rdi # 0xb052d84
27: 44 89 ee mov %r13d,%esi
* 2a: 67 48 0f b9 3a ud1 (%edx),%rdi <-- trapping instruction
2f: e9 2c 01 00 00 jmp 0x160
34: e8 3b 97 f4 06 call 0x6f49774
39: 89 c3 mov %eax,%ebx
3b: 31 ff xor %edi,%edi
3d: 89 c6 mov %eax,%esi
3f: e8 .byte 0xe8


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