[syzbot] [bcachefs?] BUG: unable to handle kernel paging request in __bch2_trans_get

[syzbot <syzbot+4b39c41aee23bac377fe@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    5f5673607153 Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=152cdc07980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=dedbcb1ff4387972
dashboard link: https://syzkaller.appspot.com/bug?extid=4b39c41aee23bac377fe
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/40172aed5414/disk-5f567360.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/58372f305e9d/vmlinux-5f567360.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d2aae6fa798f/Image-5f567360.gz.xz

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

bcachefs (loop4): recovering from clean shutdown, journal seq 10
bcachefs (loop4): Doing compatible version upgrade from 1.7: mi_btree_bitmap to 1.12: rebalance_work_acct_fix
  running recovery passes: check_allocations
Unable to handle kernel paging request at virtual address ffff0000c6b681b2
KASAN: maybe wild-memory-access in range [0xfffc000635b40d90-0xfffc000635b40d97]
Mem abort info:
  ESR = 0x0000000096000061
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x21: alignment fault
Data abort info:
  ISV = 0, ISS = 0x00000061, ISS2 = 0x00000000
  CM = 0, WnR = 1, TnD = 0, TagAccess = 0
  GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000001a60a0000
[ffff0000c6b681b2] pgd=0000000000000000, p4d=180000023ffff003, pud=180000023f41b003, pmd=180000023f3e5003, pte=0068000106b68707
Internal error: Oops: 0000000096000061 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 UID: 0 PID: 7397 Comm: syz.4.294 Not tainted 6.11.0-rc7-syzkaller-g5f5673607153 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : raw_atomic_set_release include/linux/atomic/atomic-arch-fallback.h:524 [inline]
pc : atomic_set_release include/linux/atomic/atomic-instrumented.h:87 [inline]
pc : closure_init_stack_release include/linux/closure.h:335 [inline]
pc : __bch2_trans_get+0x790/0xa64 fs/bcachefs/btree_iter.c:3205
lr : raw_atomic_set_release include/linux/atomic/atomic-arch-fallback.h:524 [inline]
lr : atomic_set_release include/linux/atomic/atomic-instrumented.h:87 [inline]
lr : closure_init_stack_release include/linux/closure.h:335 [inline]
lr : __bch2_trans_get+0x784/0xa64 fs/bcachefs/btree_iter.c:3205
sp : ffff8000a3cc6f70
x29: ffff8000a3cc6f80 x28: ffff0000c3003c80 x27: dfff800000000000
x26: 0000000000000000 x25: 1fffe00018d6d008 x24: 0000000000000002
x23: 0000000000000000 x22: ffff0000c6b68044 x21: 00000000ffffa3ad
x20: ffff0000c6b681b2 x19: ffff0000c6b68002 x18: 1fffe000366d79ee
x17: ffff80008f56d000 x16: ffff80008b274880 x15: 0000000000000001
x14: 1fffe00018d6d036 x13: 0000000000000000 x12: 0000000000000000
x11: ffff600018d6d037 x10: 1fffe00018d6d036 x9 : dfff800000000000
x8 : 0000000040000001 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 000000000000000e x3 : ffff8000827c3258
x2 : 0000000000000001 x1 : 0000000000000004 x0 : ffff0000c6b68002
Call trace:
 __bch2_trans_get+0x790/0xa64 fs/bcachefs/btree_iter.c:3206
 bch2_btree_root_read+0xc0/0x53c fs/bcachefs/btree_io.c:1773
 read_btree_roots+0x250/0x798 fs/bcachefs/recovery.c:523
 bch2_fs_recovery+0x3278/0x5514 fs/bcachefs/recovery.c:851
 bch2_fs_start+0x30c/0x53c fs/bcachefs/super.c:1036
 bch2_fs_get_tree+0x938/0x1030 fs/bcachefs/fs.c:1946
 vfs_get_tree+0x90/0x28c fs/super.c:1800
 do_new_mount+0x278/0x900 fs/namespace.c:3472
 path_mount+0x590/0xe04 fs/namespace.c:3799
 do_mount fs/namespace.c:3812 [inline]
 __do_sys_mount fs/namespace.c:4020 [inline]
 __se_sys_mount fs/namespace.c:3997 [inline]
 __arm64_sys_mount+0x45c/0x5a8 fs/namespace.c:3997
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712
 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730
 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598
Code: 978b1004 52800028 aa1303e0 72a80008 (889ffe88) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	978b1004 	bl	0xfffffffffe2c4010
   4:	52800028 	mov	w8, #0x1                   	// #1
   8:	aa1303e0 	mov	x0, x19
   c:	72a80008 	movk	w8, #0x4000, lsl #16
* 10:	889ffe88 	stlr	w8, [x20] <-- trapping instruction


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