[moderation] [fs?] BUG: unable to handle kernel paging request in do_symlinkat

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3a8a670eeeaa Merge tag 'net-next-6.5' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12378c0ca80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ce7f4ca96cdf82c7
dashboard link: https://syzkaller.appspot.com/bug?extid=55ad04ec36404f5eec76
compiler: aarch64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
CC: [bra...@kernel.org linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/384ffdcca292/non_bootable_disk-3a8a670e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a940531a9b86/vmlinux-3a8a670e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4f3cbae5be61/Image-3a8a670e.gz.xz

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

Unable to handle kernel paging request at virtual address bfff80008ac53d10
Mem abort info:
ESR = 0x0000000086000004
EC = 0x21: IABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000042480000
[bfff80008ac53d10] pgd=10000000bffff803, p4d=10000000bffff803, pud=10000000bfffe803, pmd=100000005f98e003, pte=006800005aa87f07
Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4245 Comm: syz-executor.1 Not tainted 6.4.0-syzkaller-04247-g3a8a670eeeaa #0
Hardware name: linux,dummy-virt (DT)
pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : 0xbfff80008ac53d10
lr : 0xffff80008ac53d10
sp : ffff80008aa0bd40
x29: ffff80008aa0bd40 x28: f9ff00001faf2f40 x27: 0000000000000000
x26: 0000000000000000 x25: 0000000000000000 x24: 00000000ffffff9c
x23: faff00000496a000 x22: fbff00000496f020 x21: fcff000019a52b40
x20: ffff80008aa0bdb8 x19: ffff8000821bce48 x18: 0000000000000000
x17: 0000000000000000 x16: 0000000000000000 x15: ffff80008030882c
x14: ffff800080308710 x13: ffff800081874d34 x12: ffff800080027b28
x11: ffff800080011558 x10: ffff80008187516c x9 : ffff800081874d34
x8 : ffff800080027b28 x7 : 0000000000008000 x6 : 0000000000000001
x5 : f9ff00001faf2f40 x4 : ffff8000823c6c00 x3 : 0000000000000000
x2 : 0000000000000000 x1 : f9ff00001faf2f40 x0 : 0000000000000000
Call trace:
0xbfff80008ac53d10
do_symlinkat+0x74/0x140 fs/namei.c:4501
__do_sys_symlinkat fs/namei.c:4519 [inline]
__se_sys_symlinkat fs/namei.c:4516 [inline]
__arm64_sys_symlinkat+0x50/0x68 fs/namei.c:4516
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x48/0x114 arch/arm64/kernel/syscall.c:52
el0_svc_common.constprop.0+0x44/0xe4 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x38/0xa4 arch/arm64/kernel/syscall.c:191
el0_svc+0x2c/0xb0 arch/arm64/kernel/entry-common.c:647
el0t_64_sync_handler+0xc0/0xc4 arch/arm64/kernel/entry-common.c:665
el0t_64_sync+0x19c/0x1a0 arch/arm64/kernel/entry.S:591
Code: 00000081 00000000 00000000 00000000 (ffffffff)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 00000081 udf #129
* 10: ffffffff .inst 0xffffffff ; undefined <-- 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 syzk...@googlegroups.com.

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

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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.