[syzbot] [btrfs?] WARNING in btrfs_destroy_inode (2)

[syzbot <syzbot+3f149babf28b57cee242@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    89f5e14d05b4 Merge tag 'timers_urgent_for_v6.11_rc7' of gi..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14c39f29980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=58a85aa6925a8b78
dashboard link: https://syzkaller.appspot.com/bug?extid=3f149babf28b57cee242
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 (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-89f5e14d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dfc310daee41/vmlinux-89f5e14d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a92f22c06568/bzImage-89f5e14d.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 5121 at fs/btrfs/inode.c:7729 btrfs_destroy_inode+0x323/0x7d0 fs/btrfs/inode.c:7729
Modules linked in:
CPU: 0 UID: 0 PID: 5121 Comm: syz.0.0 Not tainted 6.11.0-rc6-syzkaller-00363-g89f5e14d05b4 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:btrfs_destroy_inode+0x323/0x7d0 fs/btrfs/inode.c:7729
Code: 0f 0b 90 e9 61 fe ff ff e8 aa 07 e1 fd 90 0f 0b 90 e9 d2 fe ff ff e8 9c 07 e1 fd 90 0f 0b 90 e9 fd fe ff ff e8 8e 07 e1 fd 90 <0f> 0b 90 48 85 ed 0f 85 2d ff ff ff e8 7c 07 e1 fd 49 8d 9c 24 98
RSP: 0018:ffffc90002f9efa8 EFLAGS: 00010283
RAX: ffffffff83b28522 RBX: ffffffffffffffff RCX: 0000000000040000
RDX: ffffc9000b53a000 RSI: 000000000002e363 RDI: 000000000002e364
RBP: ffff88803d78c000 R08: ffffffff83b28445 R09: 1ffffffff2030ee5
R10: dffffc0000000000 R11: ffffffff83b28200 R12: ffff88801310b790
R13: ffff88803d78c000 R14: ffff88801310b3f0 R15: dffffc0000000000
FS:  00007ff6855786c0(0000) GS:ffff88801fe00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000556646649f88 CR3: 0000000040dba000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 destroy_inode fs/inode.c:313 [inline]
 evict+0x809/0x950 fs/inode.c:729
 btrfs_iget_path+0x124f/0x17b0 fs/btrfs/inode.c:5605
 btrfs_iget_logging fs/btrfs/tree-log.c:154 [inline]
 add_conflicting_inode fs/btrfs/tree-log.c:5680 [inline]
 copy_inode_items_to_log fs/btrfs/tree-log.c:5950 [inline]
 btrfs_log_inode+0x22bb/0x4700 fs/btrfs/tree-log.c:6613
 btrfs_log_inode_parent+0xb3e/0x1160 fs/btrfs/tree-log.c:7106
 btrfs_log_dentry_safe+0x61/0x80 fs/btrfs/tree-log.c:7207
 btrfs_sync_file+0xb60/0x11c0 fs/btrfs/file.c:1778
 generic_write_sync include/linux/fs.h:2822 [inline]
 btrfs_do_write_iter+0x5e2/0x760 fs/btrfs/file.c:1515
 do_iter_readv_writev+0x60a/0x890
 vfs_writev+0x37c/0xbb0 fs/read_write.c:971
 do_pwritev fs/read_write.c:1072 [inline]
 __do_sys_pwritev2 fs/read_write.c:1131 [inline]
 __se_sys_pwritev2+0x1ca/0x2d0 fs/read_write.c:1122
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff68477cef9
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:00007ff685578038 EFLAGS: 00000246 ORIG_RAX: 0000000000000148
RAX: ffffffffffffffda RBX: 00007ff684936058 RCX: 00007ff68477cef9
RDX: 0000000000000001 RSI: 0000000020022e80 RDI: 0000000000000008
RBP: 00007ff6847ef046 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007ff684936058 R15: 00007fff28631528
 </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 syzkaller@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