From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, tglx@linutronix.de, mingo@kernel.org,
bp@alien8.de, hpa@zytor.com, kirill@shutemov.name,
keescook@chromium.org, yamada.masahiro@socionext.com,
dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, thgarnie@google.com, mike.travis@hpe.com,
frank.ramsay@hpe.com, Baoquan He <bhe@redhat.com>
Subject: [PATCH 0/2] x86/mm/KASLR: Fix two code bugs
Date: Thu, 4 Apr 2019 10:03:12 +0800 [thread overview]
Message-ID: <20190404020314.8162-1-bhe@redhat.com> (raw)
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. We need a
specific SGI UV machine to reproduce and verify it, still discussing
with Mike and Frank from HPE SGI about arranging a machine to test. That
machine is very rare, still waiting. So defer that bug fix reposting
later.
Baoquan He (2):
x86/mm/KASLR: Fix the wrong calculation of memory region initial size
x86/mm/KASLR: Calculate the actual size of vmemmap region
arch/x86/mm/kaslr.c | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
--
2.17.2
next reply other threads:[~2019-04-04 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 2:03 Baoquan He [this message]
2019-04-04 2:03 ` [PATCH 1/2] x86/mm/KASLR: Fix the wrong calculation of memory region initial size Baoquan He
2019-04-05 16:58 ` Borislav Petkov
2019-04-05 17:22 ` Thomas Gleixner
2019-04-06 1:55 ` Baoquan He
2019-04-06 1:51 ` Baoquan He
2019-04-06 4:43 ` Borislav Petkov
2019-04-08 7:54 ` Baoquan He
2019-04-04 2:03 ` [PATCH 2/2] x86/mm/KASLR: Calculate the actual size of vmemmap region 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=20190404020314.8162-1-bhe@redhat.com \
--to=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=frank.ramsay@hpe.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mike.travis@hpe.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.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 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.