[syzbot] [btrfs?] general protection fault in prelim_ref_insert

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5076001689e4 Merge tag 'loongarch-fixes-6.13-1' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=129dade8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=50c7a61469ce77e7
dashboard link: https://syzkaller.appspot.com/bug?extid=af426748c95aef4f003e
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/7feb34a89c2a/non_bootable_disk-50760016.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/76ef343a98c8/vmlinux-50760016.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e42b3235bcc3/bzImage-50760016.xz

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

loop0: detected capacity change from 0 to 32768
BTRFS: device fsid ed167579-eb65-4e76-9a50-61ac97e9b59d devid 1 transid 8 /dev/loop0 (7:0) scanned by syz.0.0 (5320)
BTRFS info (device loop0): first mount of filesystem ed167579-eb65-4e76-9a50-61ac97e9b59d
BTRFS info (device loop0): using sha256 (sha256-avx2) checksum algorithm
BTRFS info (device loop0): rebuilding free space tree
BTRFS info (device loop0): disabling free space tree
BTRFS info (device loop0): clearing compat-ro feature flag for FREE_SPACE_TREE (0x1)
BTRFS info (device loop0): clearing compat-ro feature flag for FREE_SPACE_TREE_VALID (0x2)
BTRFS info (device loop0): balance: start -d -m
BTRFS info (device loop0): relocating block group 6881280 flags data|metadata
BTRFS info (device loop0): relocating block group 5242880 flags data|metadata
BTRFS info (device loop0): found 9 extents, stage: move data extents
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]
CPU: 0 UID: 0 PID: 5320 Comm: syz.0.0 Not tainted 6.13.0-rc1-syzkaller-00036-g5076001689e4 #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:do_perf_trace_btrfs__prelim_ref include/trace/events/btrfs.h:1926 [inline]
RIP: 0010:perf_trace_btrfs__prelim_ref+0x32d/0x7b0 include/trace/events/btrfs.h:1926
Code: fd e9 b3 02 00 00 e8 02 c1 e7 fd ba 10 00 00 00 48 89 df 31 f6 e8 93 ab 52 fe 4c 89 64 24 08 49 8d 5e 18 48 89 d8 48 c1 e8 03 <42> 80 3c 38 00 74 08 48 89 df e8 a4 a8 52 fe 4c 8b 23 49 8d 5d 18
RSP: 0018:ffffc9000d3dee00 EFLAGS: 00010206
RAX: 0000000000000003 RBX: 0000000000000018 RCX: ffffffff83b7b10d
RDX: 0000000000000010 RSI: ffff888045b0b000 RDI: ffffe8ffffc47ba0
RBP: ffffc9000d3def00 R08: 764e65eb797516ed R09: 9db5e997ac61509a
R10: 764e65eb797516ed R11: 9db5e997ac61509a R12: ffff88801fc376e0
R13: ffffe8ffffc47b98 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007fef5110b6c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055891b663b30 CR3: 00000000405ae000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
trace_btrfs_prelim_ref_insert include/trace/events/btrfs.h:1976 [inline]
prelim_ref_insert+0x1064/0x1250 fs/btrfs/backref.c:327
add_prelim_ref fs/btrfs/backref.c:414 [inline]
add_direct_ref fs/btrfs/backref.c:424 [inline]
add_inline_refs fs/btrfs/backref.c:1084 [inline]
find_parent_nodes+0x5fb2/0x7bd0 fs/btrfs/backref.c:1485
btrfs_find_all_leafs+0xca/0x2c0 fs/btrfs/backref.c:1709
add_data_references+0x275/0x1330 fs/btrfs/relocation.c:3412
relocate_block_group+0x6bb/0xd40 fs/btrfs/relocation.c:3669
btrfs_relocate_block_group+0x77d/0xd90 fs/btrfs/relocation.c:4081
btrfs_relocate_chunk+0x12c/0x3b0 fs/btrfs/volumes.c:3494
__btrfs_balance+0x1b0f/0x26b0 fs/btrfs/volumes.c:4278
btrfs_balance+0xbdc/0x10c0 fs/btrfs/volumes.c:4655
btrfs_ioctl_balance+0x493/0x7c0 fs/btrfs/ioctl.c:3670
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:906 [inline]
__se_sys_ioctl+0xf5/0x170 fs/ioctl.c:892
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:0x7fef5037ff19
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:00007fef5110b058 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fef50545fa0 RCX: 00007fef5037ff19
RDX: 0000000020000180 RSI: 00000000c4009420 RDI: 0000000000000006
RBP: 00007fef503f3986 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fef50545fa0 R15: 00007fff11d5d158
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:do_perf_trace_btrfs__prelim_ref include/trace/events/btrfs.h:1926 [inline]
RIP: 0010:perf_trace_btrfs__prelim_ref+0x32d/0x7b0 include/trace/events/btrfs.h:1926
Code: fd e9 b3 02 00 00 e8 02 c1 e7 fd ba 10 00 00 00 48 89 df 31 f6 e8 93 ab 52 fe 4c 89 64 24 08 49 8d 5e 18 48 89 d8 48 c1 e8 03 <42> 80 3c 38 00 74 08 48 89 df e8 a4 a8 52 fe 4c 8b 23 49 8d 5d 18
RSP: 0018:ffffc9000d3dee00 EFLAGS: 00010206
RAX: 0000000000000003 RBX: 0000000000000018 RCX: ffffffff83b7b10d
RDX: 0000000000000010 RSI: ffff888045b0b000 RDI: ffffe8ffffc47ba0
RBP: ffffc9000d3def00 R08: 764e65eb797516ed R09: 9db5e997ac61509a
R10: 764e65eb797516ed R11: 9db5e997ac61509a R12: ffff88801fc376e0
R13: ffffe8ffffc47b98 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007fef5110b6c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055891b663b30 CR3: 00000000405ae000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: fd std
1: e9 b3 02 00 00 jmp 0x2b9
6: e8 02 c1 e7 fd call 0xfde7c10d
b: ba 10 00 00 00 mov $0x10,%edx
10: 48 89 df mov %rbx,%rdi
13: 31 f6 xor %esi,%esi
15: e8 93 ab 52 fe call 0xfe52abad
1a: 4c 89 64 24 08 mov %r12,0x8(%rsp)
1f: 49 8d 5e 18 lea 0x18(%r14),%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 38 00 cmpb $0x0,(%rax,%r15,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 a4 a8 52 fe call 0xfe52a8dd
39: 4c 8b 23 mov (%rbx),%r12
3c: 49 8d 5d 18 lea 0x18(%r13),%rbx


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