From: Sasha Levin <sashal@kernel.org>
To: Kristina Martsenko <kristina.martsenko@arm.com>
Cc: stable@vger.kernel.org, Catalin Marinas <catalin.marinas@arm.com>,
Christoffer Dall <christoffer.dall@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: Two arm64 patches for stable
Date: Fri, 18 Jan 2019 21:07:52 -0500 [thread overview]
Message-ID: <20190119020752.GF202535@sasha-vm> (raw)
In-Reply-To: <7acde9fd-242b-0850-81b3-6dbd4cc75565@arm.com>
On Fri, Jan 18, 2019 at 05:53:38PM +0000, Kristina Martsenko wrote:
>Hi,
>
>Please apply commits
>
> 4eaed6aa2c62 ("arm64/kvm: consistently handle host HCR_EL2 flags")
> b3669b1e1c09 ("arm64: Don't trap host pointer auth use to EL2")
>
>to the 4.19.y (and 4.20.y) stable kernels. The patches prevent userspace
>from entering KVM directly on newer ARM CPUs. I'll also send backports
>for the 4.4.y, 4.9.y, and 4.14.y stable kernels in reply to this email.
I've queued these two for 4.4-4.20, thank you!
--
Thanks,
Sasha
prev parent reply other threads:[~2019-01-19 2:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 17:53 Two arm64 patches for stable Kristina Martsenko
2019-01-18 17:55 ` [PATCH 4.4 1/2] arm64/kvm: consistently handle host HCR_EL2 flags Kristina Martsenko
2019-01-18 17:55 ` [PATCH 4.4 2/2] arm64: Don't trap host pointer auth use to EL2 Kristina Martsenko
2019-01-18 17:56 ` [PATCH 4.9 1/2] arm64/kvm: consistently handle host HCR_EL2 flags Kristina Martsenko
2019-01-18 17:56 ` [PATCH 4.9 2/2] arm64: Don't trap host pointer auth use to EL2 Kristina Martsenko
2019-01-18 17:56 ` [PATCH 4.14 1/2] arm64/kvm: consistently handle host HCR_EL2 flags Kristina Martsenko
2019-01-18 17:56 ` [PATCH 4.14 2/2] arm64: Don't trap host pointer auth use to EL2 Kristina Martsenko
2019-01-19 2:07 ` Sasha Levin [this message]
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=20190119020752.GF202535@sasha-vm \
--to=sashal@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=kristina.martsenko@arm.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=stable@vger.kernel.org \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox