[bug report] KVM: arm64: BUG when reading kcore with kvm-arm.mode=protected
Oliver Upton
oliver.upton at linux.dev
Wed Oct 2 08:44:56 PDT 2024
+cc relevant folks
Hi James,
On Wed, Oct 02, 2024 at 02:23:32PM +0100, James Clark wrote:
> Hi,
>
> I noticed this when running the Perf tests so I'm reporting it here (I don't
> actually need kcore FWIW). I tested from 6.1 to 6.11 with the same results:
Yeah, this is (somewhat) intended behavior. By reading kcore you wind up
reading from memory that isn't in a visible state for the host (e.g. hyp
text).
Protected mode is very much a WIP, and is expected to be rough around the
edges like this. Eventually the hypervisor will inject an abort into the
host for disallowed memory accesses instead of tripping a BUG_ON(). We
don't have that upstream right now.
> # On the host:
> $ cat /proc/cmdline
>
> BOOT_IMAGE=/boot/vmlinuz-6.11.0-rc6+
> root=UUID=090f43e8-dbb2-48e4-a9e2-efd6291fb21f ro earlycon=pl011,0x2A400000
> kpti=off vfio-pci.ids=10ee:9038 kvm-arm.mode=protected
>
> $ sudo dd if=/proc/kcore of=/dev/null
>
> # Wait a few seconds
>
> kvm [732]: nVHE hyp BUG at: arch/arm64/kvm/hyp/nvhe/mem_protect.c:540!
> kvm [732]: nVHE call trace:
> kvm [732]: [<ffff8000090c2654>] __kvm_nvhe_$x.158+0x44/0x80
> kvm [732]: [<ffff8000090c88d4>] __kvm_nvhe_$x.90+0x34/0x124
> kvm [732]: [<ffff8000090c4844>] __kvm_nvhe_$x.1+0x4c/0x84
> kvm [732]: [<ffff8000090c3864>] __kvm_nvhe_$x.0+0x64/0x64
> kvm [732]: ---[ end nVHE call trace ]---
> kvm [732]: Hyp Offset: 0xfffeffff97e00000
> Kernel panic - not syncing: HYP panic:
> PS:a04003c9 PC:00008000712c89c8 ESR:00000000f2000800
> FAR:ffff0000712bf000 HPFAR:0000000000f12bf0 PAR:0000000000000800
> VCPU:0000000000000000
> CPU: 1 PID: 732 Comm: dd Not tainted 6.4.0+ #54
> Call trace:
> dump_backtrace+0x100/0x158
> show_stack+0x24/0x40
> dump_stack_lvl+0x60/0x80
> dump_stack+0x18/0x28
> panic+0x148/0x360
> nvhe_hyp_panic_handler+0x110/0x1a0
> _copy_to_iter+0xd8/0x520
> read_kcore_iter+0x54c/0x768
> proc_reg_read_iter+0xa0/0x118
> vfs_read+0x1b4/0x290
> ksys_read+0x80/0xf8
> __arm64_sys_read+0x28/0x40
> invoke_syscall+0x4c/0x120
> el0_svc_common+0xd0/0x120
> do_el0_svc+0x3c/0xb8
> el0_svc+0x44/0xb0
> el0t_64_sync_handler+0x84/0xf0
> el0t_64_sync+0x190/0x198
> SMP: stopping secondary CPUs
> Kernel Offset: disabled
> CPU features: 0x000000,4040180c,6400720b
> Memory Limit: none
> pstore: backend (efi_pstore) writing error (-5)
> ---[ end Kernel panic - not syncing: HYP panic:
> PS:a04003c9 PC:00008000712c89c8 ESR:00000000f2000800
> FAR:ffff0000712bf000 HPFAR:0000000000f12bf0 PAR:0000000000000800
> VCPU:0000000000000000 ]---
>
>
>
--
Thanks,
Oliver
More information about the linux-arm-kernel
mailing list