On Fri, 13 Aug 2021 14:03:36 +0100, Will Deacon wrote:

When protected mode is enabled, the host is unable to access most parts
of the EL2 hypervisor image, including 'hyp_physvirt_offset' and the
contents of the hypervisor's '.rodata.str' section. Unfortunately,
nvhe_hyp_panic_handler() tries to read from both of these locations when
handling a BUG() triggered at EL2; the former for converting the ELR to
a physical address and the latter for displaying the name of the source
file where the BUG() occurred.

[...]

Applied to kvm-arm64/mmu/el2-tracking, thanks!

[1/1] KVM: arm64: Make hyp_panic() more robust when protected mode is enabled
      commit: ccac96977243d7916053550f62e6489760ad0adc

Cheers,

	M.
-- 
Without deviation from the norm, progress is not possible.



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel