[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170321102756.795fe8ae@hananiah.suse.cz>
Date: Tue, 21 Mar 2017 10:27:56 +0100
From: Petr Tesarik <ptesarik@...e.cz>
To: Xunlei Pang <xlpang@...hat.com>
Cc: linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
Baoquan He <bhe@...hat.com>,
Eric Biederman <ebiederm@...ssion.com>,
akpm@...ux-foundation.org, Dave Young <dyoung@...hat.com>
Subject: Re: [PATCH v3 1/3] kexec: Move vmcoreinfo out of the kernel's .bss
section
On Mon, 20 Mar 2017 13:50:31 +0800
Xunlei Pang <xlpang@...hat.com> wrote:
> As Eric said,
> "what we need to do is move the variable vmcoreinfo_note out
> of the kernel's .bss section. And modify the code to regenerate
> and keep this information in something like the control page.
>
> Definitely something like this needs a page all to itself, and ideally
> far away from any other kernel data structures. I clearly was not
> watching closely the data someone decided to keep this silly thing
> in the kernel's .bss section."
>
> This patch allocates extra pages for these vmcoreinfo_XXX variables,
> one advantage is that it enhances some safety of vmcoreinfo, because
> vmcoreinfo now is kept far away from other kernel data structures.
Yes, I like this patch set very much now. Thank you!
Petr T
Powered by blists - more mailing lists