From: Baoquan He <bhe@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
x86@kernel.org, tglx@linutronix.de, mingo@kernel.org,
hpa@zytor.com, kirill.shutemov@linux.intel.com,
keescook@chromium.org
Subject: Re: [PATCH v4] x86/mm/KASLR: Fix the size of vmemmap section
Date: Wed, 8 May 2019 17:35:20 +0800 [thread overview]
Message-ID: <20190508093520.GD24922@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20190508090424.GA19015@zn.tnic>
On 05/08/19 at 11:04am, Borislav Petkov wrote:
> On Wed, May 08, 2019 at 04:24:18PM +0800, Baoquan He wrote:
> > I think this's worth noticing stable tree:
> >
> > Cc: stable@vger.kernel.org
>
> Fixes: ?
Not sure which commit validated 5-level.
Hi Kirill,
Is this commit OK?
Fiexes: eedb92abb9bb ("x86/mm: Make virtual memory layout dynamic for CONFIG_X86_5LEVEL=y")
Thanks
Baoquan
next prev parent reply other threads:[~2019-05-08 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190508080417.15074-1-bhe@redhat.com>
2019-05-08 8:24 ` [PATCH v4] x86/mm/KASLR: Fix the size of vmemmap section Baoquan He
2019-05-08 9:04 ` Borislav Petkov
2019-05-08 9:35 ` Baoquan He [this message]
2019-05-08 14:47 ` Kirill A. Shutemov
2019-05-15 1:48 ` 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=20190508093520.GD24922@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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: 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;
as well as URLs for NNTP newsgroup(s).