From: Oliver Upton <oupton@kernel.org>
To: kvmarm@lists.linux.dev
Cc: Marc Zyngier <maz@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Wei-Lin Chang <weilin.chang@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Oliver Upton <oupton@kernel.org>
Subject: [PATCH 0/2] KVM: arm64: Fixes for S2 permission relaxation
Date: Wed, 1 Jul 2026 16:16:18 -0700 [thread overview]
Message-ID: <20260701231620.3300204-1-oupton@kernel.org> (raw)
Couple of small fixes for S2 permission relaxation.
The first patch looks a bit worse than it actually is, potentially
consuming an uninitialized stack variable as a TLBI TTL hint in the
event of a race to update the PTE. However, if the bad TTL value results
in the stale TLB entry remaining valid, the vCPU will just fault again
and (hopefully) avoid the race.
Second patch is of a similar flavor, where the permission relaxation was
unconditionally updating XN, potentially reaping execute permissions
when handling a write fault. The consequence of this is taking an
unintended execute permission fault to restore the original XN value.
Applies to 7.2-rc1.
Oliver Upton (2):
KVM: arm64: Ensure level is always initialized when relaxing perms
KVM: arm64: Only update XN attr when requested during S2 relaxation
arch/arm64/kvm/hyp/pgtable.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
base-commit: dc59e4fea9d83f03bad6bddf3fa2e52491777482
--
2.47.3
next reply other threads:[~2026-07-01 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 23:16 Oliver Upton [this message]
2026-07-01 23:16 ` [PATCH 1/2] KVM: arm64: Ensure level is always initialized when relaxing perms Oliver Upton
2026-07-01 23:16 ` [PATCH 2/2] KVM: arm64: Only update XN attr when requested during S2 relaxation Oliver Upton
2026-07-02 7:16 ` [PATCH 0/2] KVM: arm64: Fixes for S2 permission relaxation Wei-Lin Chang
2026-07-06 16:19 ` Marc Zyngier
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=20260701231620.3300204-1-oupton@kernel.org \
--to=oupton@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=weilin.chang@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox