[Xen-devel] incorrect layout of globals from head_64.S during kexec boot
JBeulich at suse.com
Fri Jul 6 10:50:20 EDT 2012
>>> On 06.07.12 at 16:14, Olaf Hering <olaf at aepfle.de> wrote:
> On Fri, Jul 06, Olaf Hering wrote:
>> I will cleanup my debug changes and post the output.
> What I see is that the content of the uncompressed vmlinux is
> appearently already corrupted after decompress(). After I made small
> changes to arch/x86/boot/compressed/misc.c and arch/x86/kernel/head_64.S
> the offset in memory changed from 0x2c to 0x8.
> This could mean that the unzip code is broken, but this is rather
> unlikely. The odd thing is, if the first kernel is forced to return
> false in xen_hvm_platform() to disable the PVonHVM features then kexec
> works ok.
> Could it be that some code tweaks the stack content used by decompress()
> in some odd way? But that would most likely lead to a crash, not to
> unexpected uncompressing results.
Especially if the old and new kernel are using the exact same
image, how about the decompression writing over the shared
info page causing all this? As the decompressor wouldn't
expect Xen to possibly write stuff there itself, it could easily be
that some repeat count gets altered, thus breaking the
decompressed data without the decompression code necessarily
If that's the case, there would be a more general problem here
(for kdump at least), as granted pages could also still get written
to when the new kernel already is in the process of launching.
More information about the kexec