Hello, syzbot found the following issue on: HEAD commit: a5541c0811a0 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=13f3872f880000 kernel config: https://syzkaller.appspot.com/x/.config?x=cbd4e584773e9397 dashboard link: https://syzkaller.appspot.com/bug?extid=6f1094dbac66f87b75e5 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 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13918e67880000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10870133880000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/4b7702208fb9/disk-a5541c08.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/9ec0153ec051/vmlinux-a5541c08.xz kernel image: https://storage.googleapis.com/syzbot-assets/6f8725ad290a/Image-a5541c08.gz.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/31a0c6469932/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+6f1094dbac66f87b75e5@xxxxxxxxxxxxxxxxxxxxxxxxx loop0: detected capacity change from 0 to 64 Unable to handle kernel paging request at virtual address 003f1d3fea3fdfc7 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004 CM = 0, WnR = 0 [003f1d3fea3fdfc7] address between user and kernel address ranges Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: CPU: 0 PID: 3072 Comm: syz-executor332 Not tainted 6.1.0-rc8-syzkaller-33330-ga5541c0811a0 #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 : timestamp_truncate fs/inode.c:2448 [inline] pc : current_time+0x48/0x18c fs/inode.c:2486 lr : current_time+0x3c/0x18c fs/inode.c:2479 sp : ffff80000ff7ba40 x29: ffff80000ff7ba60 x28: 0000000000000040 x27: ffff0000c6c47618 x26: ffff0000ca57ec30 x25: 0000000000000000 x24: ffff0000cb410d58 x23: d93f1d3fea3fd93f x22: ffff0000cb410d58 x21: 0000000000008000 x20: 000000000000002b x19: 0000000007270e00 x18: 0000000000000000 x17: 0000000000000000 x16: ffff80000dbe6158 x15: ffff0000c61e3480 x14: 0000000000000008 x13: 0000000000000000 x12: ffff0000c61e3480 x11: ff808000082263ec x10: 0000000000000000 x9 : ffff8000082263ec x8 : ffff0000c61e3480 x7 : ffff8000085febdc x6 : 0000000000000000 x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000 x2 : 0000000000000006 x1 : 0000000000000000 x0 : 0000000000000000 Call trace: current_time+0x48/0x18c fs/inode.c:2486 hfs_new_inode+0xdc/0x304 fs/hfs/inode.c:203 hfs_create+0x38/0xc8 fs/hfs/dir.c:198 lookup_open fs/namei.c:3413 [inline] open_last_lookups fs/namei.c:3481 [inline] path_openat+0x804/0x11c4 fs/namei.c:3711 do_filp_open+0xdc/0x1b8 fs/namei.c:3741 do_sys_openat2+0xb8/0x22c fs/open.c:1310 do_sys_open fs/open.c:1326 [inline] __do_sys_openat fs/open.c:1342 [inline] __se_sys_openat fs/open.c:1337 [inline] __arm64_sys_openat+0xb0/0xe0 fs/open.c:1337 __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/0x140 arch/arm64/kernel/syscall.c:197 el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584 Code: 97f09d9d f9401677 b4000917 a940cff4 (f94346f6) ---[ end trace 0000000000000000 ]--- ---------------- Code disassembly (best guess): 0: 97f09d9d bl 0xffffffffffc27674 4: f9401677 ldr x23, [x19, #40] 8: b4000917 cbz x23, 0x128 c: a940cff4 ldp x20, x19, [sp, #8] * 10: f94346f6 ldr x22, [x23, #1672] <-- 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. syzbot can test patches for this issue, for details see: https://goo.gl/tpsmEJ#testing-patches
