From: Marc Zyngier <maz@kernel.org>
To: stable@vger.kernel.org
Cc: stable-commits@vger.kernel.org,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: Patch "KVM: arm64: nv: Add sanitising to VNCR-backed sysregs" has been added to the 6.8-stable tree
Date: Mon, 03 Jun 2024 13:09:52 +0100 [thread overview]
Message-ID: <86mso2kz1r.wl-maz@kernel.org> (raw)
In-Reply-To: <20240603115255.1829330-1-sashal@kernel.org>
On Mon, 03 Jun 2024 12:52:54 +0100,
Sasha Levin <sashal@kernel.org> wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> KVM: arm64: nv: Add sanitising to VNCR-backed sysregs
>
> to the 6.8-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> kvm-arm64-nv-add-sanitising-to-vncr-backed-sysregs.patch
> and it can be found in the queue-6.8 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
>
>
> commit fbb2bcdc458dd7db3860f85a06e98cc25904d20d
> Author: Marc Zyngier <maz@kernel.org>
> Date: Wed Feb 14 13:18:04 2024 +0000
>
> KVM: arm64: nv: Add sanitising to VNCR-backed sysregs
>
> [ Upstream commit 888f0880702293096619b300150cd7e59fcd9743 ]
>
> VNCR-backed "registers" are actually only memory. Which means that
> there is zero control over what the guest can write, and that it
> is the hypervisor's job to actually sanitise the content of the
> backing store. Yeah, this is fun.
>
> In order to preserve some form of sanity, add a repainting mechanism
> that makes use of a per-VM set of RES0/RES1 masks, one pair per VNCR
> register. These masks get applied on access to the backing store via
> __vcpu_sys_reg(), ensuring that the state that is consumed by KVM is
> correct.
>
> So far, nothing populates these masks, but stay tuned.
>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> Reviewed-by: Joey Gouly <joey.gouly@arm.com>
> Link: https://lore.kernel.org/r/20240214131827.2856277-4-maz@kernel.org
> Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
> Stable-dep-of: ce5d2448eb8f ("KVM: arm64: Destroy mpidr_data for 'late' vCPU creation")
> Signed-off-by: Sasha Levin <sashal@kernel.org>
Please drop this. It serves no purpose on 6.8 aside from wasting
memory. If backporting ce5d2448eb8f is hard due to some conflicts,
we'll tackle it ourselves.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
parent reply other threads:[~2024-06-03 12:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240603115255.1829330-1-sashal@kernel.org>]
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=86mso2kz1r.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=oliver.upton@linux.dev \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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.