From: Baoquan He <bhe@redhat.com>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [v5] x86/mm/KASLR: Fix the size of vmemmap section
Date: Wed, 12 Jun 2019 18:15:19 +0800 [thread overview]
Message-ID: <20190612101519.GM26148@MiWiFi-R3L-srv> (raw)
In-Reply-To: <CA+icZUXaXhvm46tA2aHO=85Lv16Y4=DOnz7OBRyfztp=i0_a5Q@mail.gmail.com>
On 06/04/19 at 01:46pm, Sedat Dilek wrote:
> [ CC me I am not subscribed to linux-stable ML ]
> [ CC Greg and Sasha ]
>
> Hi Baoquan,
>
> that should be s/Fiexes/Fixes for the "Fixes tag".
>
> OLD: Fiexes: eedb92abb9bb ("x86/mm: Make virtual memory layout dynamic
> for CONFIG_X86_5LEVEL=y")
> NEW: Fixes: eedb92abb9bb ("x86/mm: Make virtual memory layout dynamic
> for CONFIG_X86_5LEVEL=y")
>
> Also, you can add...
>
> Cc: stable@vger.kernel.org # v4.19+
>
> ...to catch the below.
>
> [ QUOTE ]
> You can see that it was added in kernel 4.17-rc1, as above. Can we just
> apply this patch to stable trees after 4.17?
Oops, I just noticed this mail today, sorry.
Boris has picked it into tip/x86/urgent. It should be in linus's tree
very soon. Appreciate your help anyway.
Thanks
Baoquan
>
> >
> > v5.1.4: Build OK!
> > v5.0.18: Build OK!
> > v4.19.45: Build OK!
> [ /QUOTE ]
>
> I had an early patchset of you tested (which included this one IIRC),
> so feel free to add my...
>
> Tested-by: Sedat Dilek <sedat.dilek@gmail.com>
>
> Hope this lands in tip or linux-stable Git.
>
> Thanks.
>
> Regards,
> - Sedat -
>
> [1] https://lore.kernel.org/patchwork/patch/1077557/
next prev parent reply other threads:[~2019-06-12 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 11:46 [v5] x86/mm/KASLR: Fix the size of vmemmap section Sedat Dilek
2019-06-12 10:15 ` Baoquan He [this message]
2019-06-12 12:48 ` Sedat Dilek
2019-06-12 13:19 ` Baoquan He
2019-06-12 13:23 ` Baoquan He
2019-06-12 13:41 ` Sedat Dilek
2019-06-12 14:11 ` 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=20190612101519.GM26148@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=stable@vger.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