[v6.1] WARNING in btrfs_create_new_inode (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0bc96de781b4 Linux 6.1.148
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1366b062580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5c8a5866886424a8
dashboard link: https://syzkaller.appspot.com/bug?extid=49eb5e727b6337c8bcdb
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/04c58ffc4a8a/disk-0bc96de7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/01cad248945e/vmlinux-0bc96de7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fc5395191c77/bzImage-0bc96de7.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 4617 at fs/btrfs/inode.c:6562 btrfs_create_new_inode+0x1a37/0x2380 fs/btrfs/inode.c:6562
Modules linked in:
CPU: 1 PID: 4617 Comm: syz.3.55 Not tainted 6.1.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:btrfs_create_new_inode+0x1a37/0x2380 fs/btrfs/inode.c:6562
Code: cf 8a 44 89 fe e8 19 76 e9 fd 0f 0b 4c 8b 64 24 08 e9 f6 fe ff ff e8 88 49 1d fe 48 c7 c7 80 72 cf 8a 44 89 fe e8 f9 75 e9 fd <0f> 0b 4c 8b 64 24 08 e9 d2 fd ff ff e8 68 49 1d fe 4c 8b 64 24 08
RSP: 0018:ffffc90003347620 EFLAGS: 00010246
RAX: 388f80f9ca0fae00 RBX: 0000000000000000 RCX: 0000000000080000
RDX: ffffc9000f8b5000 RSI: 0000000000010a23 RDI: 0000000000010a24
RBP: ffffc90003347870 R08: dffffc0000000000 R09: ffffed10171c4f34
R10: ffffed10171c4f34 R11: 1ffff110171c4f33 R12: ffff888028bac001
R13: 1ffff1100a8dfe0a R14: dffffc0000000000 R15: 00000000ffffffe4
FS: 00007f9d3f41d6c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fad08b5e000 CR3: 0000000020b9b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btrfs_create_common+0x173/0x230 fs/btrfs/inode.c:6791
lookup_open fs/namei.c:3482 [inline]
open_last_lookups fs/namei.c:3550 [inline]
path_openat+0x1187/0x2e70 fs/namei.c:3780
do_filp_open+0x1c1/0x3c0 fs/namei.c:3810
do_sys_openat2+0x142/0x490 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_creat fs/open.c:1412 [inline]
__se_sys_creat fs/open.c:1406 [inline]
__x64_sys_creat+0x8c/0xb0 fs/open.c:1406
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f9d3e58ebe9
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:00007f9d3f41d038 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f9d3e7b6090 RCX: 00007f9d3e58ebe9
RDX: 0000000000000000 RSI: 00000000000001a2 RDI: 0000200000000100
RBP: 00007f9d3e611e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f9d3e7b6128 R14: 00007f9d3e7b6090 R15: 00007ffe1e371d58
</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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.