[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Kernel panic with tboot E820_UNUSABLE region

Hi everybody,

We noticed a crash in Linux dom0 early boot sequence when running over
tboot and Xen. The issue seemed related with a E820 region that tboot is
setting as E820_UNUSABLE. We posted to tboot-devel to understand better
what could be the cause of the kernel panic. This thread can be read
here :

Following Konrad's advice, we took a closer look at arch/x86/xen/setup.c
and found what could be the cause of the kernel panic. I am not familiar
with that part of Xen, so feel free to correct me.

The Xen memory setup code called during early boot is trying to release
chunks of memory in xen_set_identity_and_release for non-RAM regions
(including E820_UNUSABLE). The xen_set_identity_and_release_chunk
function is calling HYPERVISOR_update_va_mapping, which will fail in our
case. As tboot marked that region as being unusable, Xen did not map
those pages and the later call on get_page_from_l1e (arch/x86/mm.c in
Xen code) is returning an error.  As the return value of the hypercall
is not checked in Linux code, xen_set_identity_and_release_chunk
function is carrying on and tries to release the E820_UNUSABLE chunk.
This is apparently messing up some Xen internal memory structures,
resulting in a kernel crash when Linux is initializing its memory mapping.

A possible fix I have tried is to check the return value of
HYPERVISOR_update_va_mapping and if encountering an error, exit from
xen_set_identity_and_release_chunk. This is fixing the kernel panic, but
I am not sure about other implications by that change.

Any ideas about this issue ?

Thanks in advance,

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.