[v6.6] WARNING in btrfs_create_new_inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 59a2de10b81a Linux 6.6.97
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=161690f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ac0b29aca872266f
dashboard link: https://syzkaller.appspot.com/bug?extid=0be0c8ad07ca18159cf5
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/32864b54a55c/disk-59a2de10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b0bbe4ada642/vmlinux-59a2de10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e3fe91e14c2/bzImage-59a2de10.xz

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

------------[ cut here ]------------
BTRFS: Transaction aborted (error -28)
WARNING: CPU: 0 PID: 6445 at fs/btrfs/inode.c:6318 btrfs_create_new_inode+0x1a58/0x2210 fs/btrfs/inode.c:6318
Modules linked in:
CPU: 0 PID: 6445 Comm: syz.1.134 Not tainted 6.6.97-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:btrfs_create_new_inode+0x1a58/0x2210 fs/btrfs/inode.c:6318
Code: 0b fe 48 c7 c7 c0 0c ed 8a 89 de e8 62 58 d6 fd 0f 0b e9 ae fe ff ff e8 f6 f3 0b fe 48 c7 c7 c0 0c ed 8a 89 de e8 48 58 d6 fd <0f> 0b e9 3a fc ff ff e8 dc f3 0b fe 4c 8b 64 24 08 e9 dc e8 ff ff
RSP: 0018:ffffc90003377a40 EFLAGS: 00010246
RAX: fb09eb4eb6072d00 RBX: 00000000ffffffe4 RCX: 0000000000080000
RDX: ffffc9000e55f000 RSI: 0000000000023350 RDI: 0000000000023351
RBP: ffffc90003377c90 R08: ffffffff90da665f R09: 1ffffffff21b4ccb
R10: dffffc0000000000 R11: fffffbfff21b4ccc R12: ffff88804f7e8001
R13: 1ffff1100bc62034 R14: dffffc0000000000 R15: 0000000000000000
FS: 00007fe8319ff6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fecc545df98 CR3: 000000004f111000 CR4: 00000000003506f0
Call Trace:
<TASK>
btrfs_create_common+0x177/0x240 fs/btrfs/inode.c:6544
vfs_mkdir+0x296/0x440 fs/namei.c:4113
do_mkdirat+0x1d4/0x440 fs/namei.c:4136
__do_sys_mkdirat fs/namei.c:4151 [inline]
__se_sys_mkdirat fs/namei.c:4149 [inline]
__x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4149
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fe831b8e929
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:00007fe8319ff038 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fe831db6080 RCX: 00007fe831b8e929
RDX: 0000000000000000 RSI: 0000200000000340 RDI: 0000000000000003
RBP: 00007fe831c10b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fe831db6080 R15: 00007fff73b5a838
</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.