[syzbot] BUG: unable to handle kernel NULL pointer dereference in __get_metapage

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit:    bbed346d5a96 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=11143afc880000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3a4a45d2d827c1e
dashboard link: https://syzkaller.appspot.com/bug?extid=3367cd73f9cc686a9763
compiler:       Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e8e91bc79312/disk-bbed346d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c1cb3fb3b77e/vmlinux-bbed346d.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+3367cd73f9cc686a9763@xxxxxxxxxxxxxxxxxxxxxxxxx

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000030
Mem abort info:
  ESR = 0x0000000096000006
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x06: level 2 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000006
  CM = 0, WnR = 0
user pgtable: 4k pages, 48-bit VAs, pgdp=0000000156537000
[0000000000000030] pgd=080000015320e003, p4d=080000015320e003, pud=08000001530cd003, pmd=0000000000000000
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 15207 Comm: syz-executor.2 Not tainted 6.0.0-rc7-syzkaller-18095-gbbed346d5a96 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __get_metapage+0xd4/0x7e0
lr : __get_metapage+0xa0/0x7e0 fs/jfs/jfs_metapage.c:600
sp : ffff80001f743a50
x29: ffff80001f743a50 x28: 000000000000000c x27: 0000000000000000
x26: ffff80000d532000 x25: 0000000000001000 x24: 000000000000000b
x23: 0000000000001000 x22: ffff0001122b1e88 x21: 0000000000000001
x20: 0000000000000000 x19: 000000000000000b x18: 00000000000000a5
x17: ffff80000bffd6bc x16: ffff80000db49158 x15: ffff0001233a3500
x14: 0000000000000008 x13: 00000000ffffffff x12: 0000000000040000
x11: 000000000000a262 x10: ffff800018655000 x9 : ffff800008d539c4
x8 : 0000000000000000 x7 : ffff8000085e8ba4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000001
x2 : 0000000000001000 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
 __get_metapage+0xd4/0x7e0
 diReadSpecial+0xf0/0x218 fs/jfs/jfs_imap.c:443
 jfs_mount+0xf4/0x468 fs/jfs/jfs_mount.c:108
 jfs_fill_super+0x188/0x454 fs/jfs/super.c:556
 mount_bdev+0x1b8/0x210 fs/super.c:1400
 jfs_do_mount+0x44/0x58 fs/jfs/super.c:670
 legacy_get_tree+0x30/0x74 fs/fs_context.c:610
 vfs_get_tree+0x40/0x140 fs/super.c:1530
 do_new_mount+0x1dc/0x4e4 fs/namespace.c:3040
 path_mount+0x358/0x914 fs/namespace.c:3370
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount fs/namespace.c:3568 [inline]
 __arm64_sys_mount+0x2c4/0x3c4 fs/namespace.c:3568
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall arch/arm64/kernel/syscall.c:52 [inline]
 el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x48/0x164 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:636
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:654
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
Code: eb15033f 540006e2 97d53089 aa1603e8 (f9401915) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	eb15033f 	cmp	x25, x21
   4:	540006e2 	b.cs	0xe0  // b.hs, b.nlast
   8:	97d53089 	bl	0xffffffffff54c22c
   c:	aa1603e8 	mov	x8, x22
* 10:	f9401915 	ldr	x21, [x8, #48] <-- 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@xxxxxxxxxxxxxxxx.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.