[syzbot] kernel BUG in trans_pgd_create_copy

[Rongwei Wang]

On 11/6/21 3:48 PM, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    d4439a1189f9 Merge tag 'hsi-for-5.16' of git://git.kernel...
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=12b5f782b00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=8eccc5e89b1d525c
> dashboard link: https://syzkaller.appspot.com/bug?extid=a0d68c9c9123000ed5ab
> compiler:       aarch64-linux-gnu-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
> userspace arch: arm
> 
> Unfortunately, I don't have any reproducer for this issue yet.
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+a0d68c9c9123000ed5ab at syzkaller.appspotmail.com
> 
> ------------[ cut here ]------------
> kernel BUG at arch/arm64/include/asm/pgalloc.h:79!
> Internal error: Oops - BUG: 0 [#1] SMP
> Modules linked in:
> CPU: 0 PID: 12093 Comm: syz-executor.1 Not tainted 5.15.0-syzkaller-10158-gd4439a1189f9 #0
> Hardware name: linux,dummy-virt (DT)
> pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> pc : pmd_populate_kernel arch/arm64/include/asm/pgalloc.h:79 [inline]
> pc : copy_pte arch/arm64/mm/trans_pgd.c:70 [inline]
> pc : copy_pmd arch/arm64/mm/trans_pgd.c:105 [inline]
> pc : copy_pud arch/arm64/mm/trans_pgd.c:141 [inline]
> pc : copy_p4d arch/arm64/mm/trans_pgd.c:167 [inline]
> pc : copy_page_tables arch/arm64/mm/trans_pgd.c:186 [inline]
> pc : trans_pgd_create_copy+0x5bc/0x7f0 arch/arm64/mm/trans_pgd.c:213
> lr : trans_alloc arch/arm64/mm/trans_pgd.c:30 [inline]
> lr : copy_pte arch/arm64/mm/trans_pgd.c:67 [inline]
> lr : copy_pmd arch/arm64/mm/trans_pgd.c:105 [inline]
> lr : copy_pud arch/arm64/mm/trans_pgd.c:141 [inline]
> lr : copy_p4d arch/arm64/mm/trans_pgd.c:167 [inline]
> lr : copy_page_tables arch/arm64/mm/trans_pgd.c:186 [inline]
> lr : trans_pgd_create_copy+0x480/0x7f0 arch/arm64/mm/trans_pgd.c:213
> sp : ffff80001b977a60
> x29: ffff80001b977a60 x28: 1fffe0000ffff000 x27: ffff800010059c90
> x26: ffff00003fffffff x25: ffff000032476000 x24: dfff800000000000
> x23: ffff000000200000 x22: ffff80001b977c30 x21: ffff000040000000
> x20: ffff00007fff8000 x19: ffff000000000000 x18: fffffbffeff9c3c8
> x17: 0000000000000000 x16: 0000000000000000 x15: d503201fd503201f
> x14: 1ffff0000372ee30 x13: 0000000000000000 x12: ffff60000648f000
> x11: 1fffe0000648efff x10: ffff60000648efff x9 : 0000000000000000
> x8 : ffff000032478000 x7 : 0000000000000000 x6 : 000000000000003f
> x5 : 0000000000000040 x4 : 0000000000000000 x3 : 0000000000000004
> x2 : fffffc0000000000 x1 : ffff800015f1e560 x0 : ffff000032477000
> Call trace:
>   set_p4d arch/arm64/include/asm/pgtable.h:695 [inline]
>   __p4d_populate arch/arm64/include/asm/pgalloc.h:46 [inline]
>   p4d_populate arch/arm64/include/asm/pgalloc.h:54 [inline]
>   copy_pud arch/arm64/mm/trans_pgd.c:129 [inline]
>   copy_p4d arch/arm64/mm/trans_pgd.c:167 [inline]
>   copy_page_tables arch/arm64/mm/trans_pgd.c:186 [inline]
>   trans_pgd_create_copy+0x5bc/0x7f0 arch/arm64/mm/trans_pgd.c:213
>   machine_kexec_post_load+0x178/0x6d0 arch/arm64/kernel/machine_kexec.c:146
>   do_kexec_load+0x194/0x520 kernel/kexec.c:155
>   __do_compat_sys_kexec_load kernel/kexec.c:292 [inline]
>   __se_compat_sys_kexec_load kernel/kexec.c:257 [inline]
>   __arm64_compat_sys_kexec_load+0x36c/0x47c kernel/kexec.c:257
>   __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
>   invoke_syscall+0x6c/0x260 arch/arm64/kernel/syscall.c:52
>   el0_svc_common.constprop.0+0xc4/0x254 arch/arm64/kernel/syscall.c:142
>   do_el0_svc_compat+0x40/0x80 arch/arm64/kernel/syscall.c:187
>   el0_svc_compat+0x64/0x280 arch/arm64/kernel/entry-common.c:736
>   el0t_32_sync_handler+0x90/0x140 arch/arm64/kernel/entry-common.c:746
>   el0t_32_sync+0x1a4/0x1a8 arch/arm64/kernel/entry.S:577
> Code: 17fffee0 aa1503e0 97ffdd37 17ffff17 (d4210000)
> ---[ end trace a6c0112af29130b0 ]---
> 
> 
This bug seems like that I described in last week:
link: 
https://patchwork.kernel.org/project/linux-arm-kernel/patch/20211030183200.51295-2-rongwei.wang@linux.alibaba.com/

> ---
> 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 at googlegroups.com.
> 
> syzbot will keep track of this issue. See:
> https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>