[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190412070257.GB7454@localhost.localdomain>
Date: Fri, 12 Apr 2019 15:02:57 +0800
From: Baoquan He <bhe@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: x86@...nel.org, tglx@...utronix.de, mingo@...nel.org, bp@...en8.de,
hpa@...or.com, kirill@...temov.name, keescook@...omium.org,
peterz@...radead.org, thgarnie@...gle.com,
herbert@...dor.apana.org.au, mike.travis@....com,
frank.ramsay@....com, yamada.masahiro@...ionext.com
Subject: Re: [PATCH v2 0/2] x86/mm/KASLR: Fix the wrong size of memory
sections
On 04/12/19 at 02:55pm, Baoquan He wrote:
> v1->v2:
> Rewrite log of the two patches. No functionality change.
~~ Sorry, I meant no new code change.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> v1 background:
> The fixes for these two bugs were carried in the earlier patchset, patch
> 4/6 and patch 5/6:
>
> [PATCH v4 0/6] Several patches to fix code bugs, improve documents and clean up
> http://lkml.kernel.org/r/20190314094645.4883-1-bhe@redhat.com
>
> Later, Thomas suggested posting bug fixing patches separately from those
> clean up patches. So send both of them in a separate patchset.
>
> For another bug fix patch 6/6, it happened on SGI UV system. Mike and
> Frank have sent a machine with cards to our lab and loaned to me, I am
> still debugging and discussing with Mike about the verification.
>
> Baoquan He (2):
> x86/mm/KASLR: Fix the size of the direct mapping section
> x86/mm/KASLR: Fix the size of vmemmap section
>
> arch/x86/mm/kaslr.c | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
> --
> 2.17.2
>
Powered by blists - more mailing lists