From: Chao Fan <fanc.fnst@cn.fujitsu.com> To: Baoquan He <bhe@redhat.com> Cc: <linux-kernel@vger.kernel.org>, <mingo@kernel.org>, <matt@codeblueprint.co.uk>, <keescook@chromium.org>, <tglx@linutronix.de>, <hpa@zytor.com>, <izumi.taku@jp.fujitsu.com>, <thgarnie@google.com>, <n-horiguchi@ah.jp.nec.com>, <ard.biesheuvel@linaro.org>, <linux-efi@vger.kernel.org>, <x86@kernel.org> Subject: Re: [PATCH v8 0/2] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions Date: Fri, 4 Aug 2017 17:59:11 +0800 [thread overview] Message-ID: <20170804095911.GD32462@localhost.localdomain> (raw) In-Reply-To: <20170804092241.GH1874@x1> On Fri, Aug 04, 2017 at 05:22:41PM +0800, Baoquan He wrote: >On 08/04/17 at 03:52pm, Baoquan He wrote: >> Sorry, NACK this series, there's error to hang system. Before I just >> halt system intentionally with error() to check the efi memmap printing, >> didn't notice this. Checking the cause. > >I rebuilt the code or change the one of the replacement back, hang never >seen again. Not sure if I copied the wrong kernel or any other mistakes. >Have got a hardware system with efi enabled to try again, see if >anything wrong will happen. It's really weird. And Chao also is helping >to try on his side. Hi Bao, After testing for 10 times, no problem happened. Maybe you did something wrong in the first time. Thanks, Chao Fan > >> >> On 08/04/17 at 03:26pm, Baoquan He wrote: >> > Patch 1/2 is newly added to add efi_memdesc_ptr helper to wrap the >> > open code which gets the start of efi memmap descriptor and also >> > explain why it need be done like that, Ingo suggested it. >> > >> > And also replace several places of the open code with efi_memdesc_ptr >> > helper. >> > >> > And also use efi_memdesc_ptr in process_efi_entries() which handle efi >> > mirror issue during KASLR. >> > >> > >> > Change: >> > v7->v8: >> > Add efi_memdesc_ptr helper to wrap the open code which gets the >> > start of map descriptor according to Ingo's suggestion. >> > >> > v6->v7: >> > Ingo pointed out several incorrect line break issues and unclear >> > description of patch log. Correct them and rewrite patch log. >> > >> > And also rewrite the EFI warning message that if EFI memmap is above >> > 4G in 32bit system since 32bit system can not handle data above 4G at >> > kernel decompression stage. This is suggested by Ingo too. >> > >> > v5->v6: >> > Code style issue fix according to Kees's comment. >> > >> > This is based on tip/x86/boot, patch 1,2,3/4 in v5 post has >> > been put into tip/x86/boot now. >> > >> > >> > >> > Baoquan He (2): >> > efi: Introduce efi_memdesc_ptr to get pointer to memmap descriptor >> > x86/boot/KASLR: Restrict kernel to be randomized in mirror regions >> > >> > arch/x86/boot/compressed/eboot.c | 2 +- >> > arch/x86/boot/compressed/kaslr.c | 68 +++++++++++++++++++++++++- >> > drivers/firmware/efi/libstub/efi-stub-helper.c | 4 +- >> > include/linux/efi.h | 19 +++++++ >> > 4 files changed, 88 insertions(+), 5 deletions(-) >> > >> > -- >> > 2.5.5 >> > > >
WARNING: multiple messages have this Message-ID (diff)
From: Chao Fan <fanc.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> To: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org, keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org, tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org, hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org, izumi.taku-+CUm20s59erQFUHtdCDX3A@public.gmane.org, thgarnie-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, n-horiguchi-PaJj6Psr51x8UrSeD/g0lQ@public.gmane.org, ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org Subject: Re: [PATCH v8 0/2] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions Date: Fri, 4 Aug 2017 17:59:11 +0800 [thread overview] Message-ID: <20170804095911.GD32462@localhost.localdomain> (raw) In-Reply-To: <20170804092241.GH1874@x1> On Fri, Aug 04, 2017 at 05:22:41PM +0800, Baoquan He wrote: >On 08/04/17 at 03:52pm, Baoquan He wrote: >> Sorry, NACK this series, there's error to hang system. Before I just >> halt system intentionally with error() to check the efi memmap printing, >> didn't notice this. Checking the cause. > >I rebuilt the code or change the one of the replacement back, hang never >seen again. Not sure if I copied the wrong kernel or any other mistakes. >Have got a hardware system with efi enabled to try again, see if >anything wrong will happen. It's really weird. And Chao also is helping >to try on his side. Hi Bao, After testing for 10 times, no problem happened. Maybe you did something wrong in the first time. Thanks, Chao Fan > >> >> On 08/04/17 at 03:26pm, Baoquan He wrote: >> > Patch 1/2 is newly added to add efi_memdesc_ptr helper to wrap the >> > open code which gets the start of efi memmap descriptor and also >> > explain why it need be done like that, Ingo suggested it. >> > >> > And also replace several places of the open code with efi_memdesc_ptr >> > helper. >> > >> > And also use efi_memdesc_ptr in process_efi_entries() which handle efi >> > mirror issue during KASLR. >> > >> > >> > Change: >> > v7->v8: >> > Add efi_memdesc_ptr helper to wrap the open code which gets the >> > start of map descriptor according to Ingo's suggestion. >> > >> > v6->v7: >> > Ingo pointed out several incorrect line break issues and unclear >> > description of patch log. Correct them and rewrite patch log. >> > >> > And also rewrite the EFI warning message that if EFI memmap is above >> > 4G in 32bit system since 32bit system can not handle data above 4G at >> > kernel decompression stage. This is suggested by Ingo too. >> > >> > v5->v6: >> > Code style issue fix according to Kees's comment. >> > >> > This is based on tip/x86/boot, patch 1,2,3/4 in v5 post has >> > been put into tip/x86/boot now. >> > >> > >> > >> > Baoquan He (2): >> > efi: Introduce efi_memdesc_ptr to get pointer to memmap descriptor >> > x86/boot/KASLR: Restrict kernel to be randomized in mirror regions >> > >> > arch/x86/boot/compressed/eboot.c | 2 +- >> > arch/x86/boot/compressed/kaslr.c | 68 +++++++++++++++++++++++++- >> > drivers/firmware/efi/libstub/efi-stub-helper.c | 4 +- >> > include/linux/efi.h | 19 +++++++ >> > 4 files changed, 88 insertions(+), 5 deletions(-) >> > >> > -- >> > 2.5.5 >> > > >
next prev parent reply other threads:[~2017-08-04 9:59 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-08-04 7:26 [PATCH v8 0/2] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions Baoquan He 2017-08-04 7:26 ` Baoquan He 2017-08-04 7:26 ` [PATCH v8 1/2] efi: Introduce efi_memdesc_ptr to get pointer to memmap descriptor Baoquan He 2017-08-04 7:26 ` [PATCH v8 2/2] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions Baoquan He 2017-08-04 7:52 ` [PATCH v8 0/2] " Baoquan He 2017-08-04 7:52 ` Baoquan He 2017-08-04 9:22 ` Baoquan He 2017-08-04 9:22 ` Baoquan He 2017-08-04 9:45 ` Chao Fan 2017-08-04 9:45 ` Chao Fan 2017-08-04 9:59 ` Chao Fan [this message] 2017-08-04 9:59 ` Chao Fan 2017-08-04 10:43 ` 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=20170804095911.GD32462@localhost.localdomain \ --to=fanc.fnst@cn.fujitsu.com \ --cc=ard.biesheuvel@linaro.org \ --cc=bhe@redhat.com \ --cc=hpa@zytor.com \ --cc=izumi.taku@jp.fujitsu.com \ --cc=keescook@chromium.org \ --cc=linux-efi@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=matt@codeblueprint.co.uk \ --cc=mingo@kernel.org \ --cc=n-horiguchi@ah.jp.nec.com \ --cc=tglx@linutronix.de \ --cc=thgarnie@google.com \ --cc=x86@kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.