From: "Thomas D." <whissi@whissi.de>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Kexec Mailing List <kexec@lists.infradead.org>,
WANG Chao <chaowang@redhat.com>, Baoquan He <bhe@redhat.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y is set
Date: Fri, 22 Aug 2014 15:23:32 +0200 [thread overview]
Message-ID: <53F74454.7000405@whissi.de> (raw)
In-Reply-To: <20140822124032.GE5954@redhat.com>
Hi,
the patch works!
I am able to reboot my system using kexec when the kernel has this patch.
I had to slightly modify the patch, so it will apply against linux-3.15.10:
--- arch/x86/boot/compressed/misc.c.old 2014-08-22 14:52:20.792158801 +0200
+++ arch/x86/boot/compressed/misc.c 2014-08-22 14:58:21.250506919 +0200
@@ -230,8 +230,9 @@
asm("hlt");
}
-#if CONFIG_X86_NEED_RELOCS
-static void handle_relocations(void *output, unsigned long output_len)
+#ifdef CONFIG_X86_NEED_RELOCS
+static void handle_relocations(void *output_orig, void *output,
+ unsigned long output_len)
{
int *reloc;
unsigned long delta, map, ptr;
@@ -242,7 +243,7 @@
* Calculate the delta between where vmlinux was linked to load
* and where it was actually loaded.
*/
- delta = min_addr - LOAD_PHYSICAL_ADDR;
+ delta = min_addr - (unsigned long)output_orig;
if (!delta) {
debug_putstr("No relocation needed... ");
return;
@@ -299,7 +300,8 @@
#endif
}
#else
-static inline void handle_relocations(void *output, unsigned long
output_len)
+static inline void handle_relocations(void *output_orig, void *output,
+ unsigned long output_len)
{ }
#endif
@@ -360,6 +362,8 @@
unsigned char *output,
unsigned long output_len)
{
+ unsigned char *output_orig = output;
+
real_mode = rmode;
sanitize_boot_params(real_mode);
@@ -402,7 +406,7 @@
debug_putstr("\nDecompressing Linux... ");
decompress(input_data, input_len, NULL, NULL, output, NULL, error);
parse_elf(output);
- handle_relocations(output, output_len);
+ handle_relocations(output_orig, output, output_len);
debug_putstr("done.\nBooting the kernel.\n");
return output;
}
So now we have two "solutions":
1) Using kexec with "--entry-32bit" parameter
2) Use a patched kernel
-Thomas
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-08-22 13:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 21:02 kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y is set Thomas D.
2014-08-18 14:57 ` Vivek Goyal
2014-08-19 9:07 ` WANG Chao
2014-08-20 14:33 ` Vivek Goyal
2014-08-21 15:57 ` Kees Cook
2014-08-21 18:10 ` Vivek Goyal
2014-08-21 19:02 ` Vivek Goyal
2014-08-21 19:27 ` Thomas D.
2014-08-22 18:18 ` Kexec failing in handle_relocations() (Was: Re: kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y is set) Vivek Goyal
2014-08-21 19:16 ` kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y is set Vivek Goyal
2014-08-22 3:19 ` WANG Chao
2014-08-22 11:59 ` Baoquan He
2014-08-22 12:30 ` Thomas D.
2014-08-22 12:40 ` Vivek Goyal
2014-08-22 13:23 ` Thomas D. [this message]
2014-08-22 13:16 ` Vivek Goyal
2014-08-22 14:44 ` Baoquan He
2014-08-22 12:38 ` Vivek Goyal
2014-08-22 12:47 ` Thomas D.
2014-08-22 12:53 ` Vivek Goyal
2014-08-22 14:59 ` Baoquan He
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53F74454.7000405@whissi.de \
--to=whissi@whissi.de \
--cc=bhe@redhat.com \
--cc=chaowang@redhat.com \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox