From: sashiko-bot@kernel.org
To: "Steffen Eiden" <seiden@linux.ibm.com>
Cc: kvmarm@lists.linux.dev, kvm@vger.kernel.org,
linux-s390@vger.kernel.org, "Oliver Upton" <oupton@kernel.org>,
"Marc Zyngier" <maz@kernel.org>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v3 20/23] KVM: s390: arm64: Finalize page fault handling
Date: Fri, 06 Nov 2026 20:10:42 +0000 [thread overview]
Message-ID: <sashiko-outbox-202185@kernel.org> (raw)
In-Reply-To: <20261106-sysreg-v3-20-75e95980fb10@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] KVM: s390: arm64: preemptible smp_processor_id() in fault
injection
--
commit 2432a7ede0d5feb054800e41b623b3e845ffe9c3
Author: Steffen Eiden <seiden@linux.ibm.com>
KVM: s390: arm64: Finalize page fault handling
This commit replaces temporary -ENOEXEC returns in the arm64-on-s390 page
fault handler with address size fault and synchronous external abort
injection into the guest, and bounds the guest address limit and
ID_AA64MMFR0_EL1.PARANGE against the supported physical address range.
> diff --git a/arch/s390/kvm/arm64/mmu.c b/arch/s390/kvm/arm64/mmu.c
> index 31e0d036896f1..7a6f6ba326c13 100644
> --- a/arch/s390/kvm/arm64/mmu.c
> +++ b/arch/s390/kvm/arm64/mmu.c
[ ... ]
> @@ -32,12 +33,14 @@ static int user_mem_abort(struct kvm_vcpu *vcpu, gpa_t fault_ipa,
> ret = kvm_s390_faultin_gfn(vcpu, NULL, &f);
> if (ret <= 0)
> return ret;
> - if (ret == PGM_ADDRESSING)
> + if (ret == PGM_ADDRESSING) {
> /*
> - * Without the relevant sysregs we cannot do anything for now.
> - * Go back to userspace with an error. TODO sysreg handling
> + * There is no page with the requested address. Inject size fault
> + * which is the closest arm match to PGM-addressing
> */
> - return -ENOEXEC;
> + kvm_inject_size_fault(vcpu);
> + return 1;
> + }
> KVM_BUG_ON(ret, vcpu->kvm);
> return -EINVAL;
> }
[ ... ]
> @@ -98,16 +130,17 @@ int kvm_handle_guest_abort(struct kvm_vcpu *vcpu)
> }
>
> if (translation) {
> - /*
> - * For both cases:
> - * Without the relevant sysregs we cannot do anything for now.
> - * Go back to userspace with an error. TODO sysreg handling
> - */
> - if (fault_ipa >= BIT_ULL(get_kvm_ipa_limit()))
> - return -ENOEXEC;
> + /* Beyond the PA range programmed for the guest */
> + if (fault_ipa >= kvm_get_pa_address(vcpu->kvm)) {
> + kvm_inject_size_fault(vcpu);
> + return 1;
> + }
>
> - if (fault_ipa >= vcpu->kvm->arch.guest_phys_size)
> - return -ENOEXEC;
> + /* Falls between the IPA range and the PA range? */
> + if (fault_ipa >= vcpu->kvm->arch.guest_phys_size) {
> + fault_ipa |= FAR_TO_FIPA_OFFSET(kvm_vcpu_get_hfar(vcpu));
> + return kvm_inject_sea(vcpu, is_iabt, fault_ipa);
> + }
> }
[Severity: Medium]
Can calling kvm_inject_size_fault() and kvm_inject_sea() (as well as
kvm_inject_sea_iabt() and kvm_inject_sea_dabt() below) from
kvm_handle_guest_abort() invoke smp_processor_id() in preemptible context?
kvm_arch_vcpu_ioctl_run() calls handle_exit() -> kvm_handle_guest_abort()
with both interrupts and preemption enabled while the vCPU is loaded
(vcpu->cpu != -1). The fault injection helpers access FAR_EL1 and ESR_EL1
through vcpu_read_sys_reg() and vcpu_write_sys_reg(), which expand to
_vcpu_read_sys_reg() and _vcpu_write_sys_reg():
arch/s390/include/asm/kvm_host_arm64.h:_vcpu_write_sys_reg() {
({ BUILD_BUG_ON(!__builtin_constant_p((R))); \
KVM_BUG_ON(vcpu_is_loaded(C) && smp_processor_id() != (C)->cpu, (C)->kvm); \
(vcpu_is_loaded(C)) \
? __vcpu_write_sr((C), (V), (R), 0) \
: __vcpu_write_sr((C), (V), (R), SASR_FLAG_INITIALIZED); })
}
When a guest faults on an address above its IPA or PA range, this triggers
a debug_smp_processor_id() warning under CONFIG_DEBUG_PREEMPT=y, and if
the vCPU thread is preempted and migrated to another CPU between reading
vcpu->cpu and smp_processor_id() (where kvm_sched_out() / kvm_sched_in()
update vcpu->cpu), KVM_BUG_ON() fires and marks the VM bugged.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106-sysreg-v3-0-75e95980fb10@linux.ibm.com?part=20
next prev parent reply other threads:[~2026-11-06 20:10 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 16:07 [PATCH v3 00/23] KVM: arm64 on s390 System Register Handling Steffen Eiden
2026-11-06 16:07 ` [PATCH v3 01/23] KVM: arm64: Refactor idreg caching into dedicated structure Steffen Eiden
2026-11-06 16:23 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 02/23] KVM: arm64: Extract number of sys_reg_desc into a constant Steffen Eiden
2026-11-06 16:25 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 03/23] arm64: sysreg: Convert OSLSR to automatic register generation Steffen Eiden
2026-11-06 16:34 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 04/23] arm64: Prepare headers for sysreg sharing with s390 Steffen Eiden
2026-11-06 16:38 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 05/23] arm64: Share system register related headers and functions " Steffen Eiden
2026-11-06 16:58 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 06/23] KVM: s390: arm64: Prepare for sharing arm64 SVE and ftr-reg code Steffen Eiden
2026-11-06 17:05 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 07/23] KVM: arm64: Prepare sys_regs.c for sharing with s390 Steffen Eiden
2026-11-06 17:06 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 08/23] KVM: arm64: Share system register code " Steffen Eiden
2026-11-06 17:18 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 09/23] s390: tools: Share arm64/kvm headers Steffen Eiden
2026-11-06 17:20 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 10/23] s390: Add range check asm macro Steffen Eiden
2026-11-06 17:23 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 11/23] s390: Read/write ARM system registers Steffen Eiden
2026-11-06 17:34 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 12/23] s390: Query arm guest time Steffen Eiden
2026-11-06 17:37 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 13/23] KVM: s390: arm64: Query Available Arm features Steffen Eiden
2026-11-06 17:45 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 14/23] KVM: s390: arm64: Verify machine feature set before loading Steffen Eiden
2026-11-06 17:49 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 15/23] KVM: s390: arm64: Implement feature sanitisation Steffen Eiden
2026-11-06 18:17 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 16/23] KVM: s390: arm64: Implement arm sysreg managing infrastructure Steffen Eiden
2026-11-06 18:45 ` sashiko-bot
2026-11-07 14:08 ` Andreas Grapentin
2026-11-06 16:07 ` [PATCH v3 17/23] KVM: s390: arm64: Integrate sysreg into the host Steffen Eiden
2026-11-06 19:18 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 18/23] KVM: s390: arm64: Use QAAF init save area Steffen Eiden
2026-11-06 19:23 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 19/23] KVM: s390: arm64: Implement exception injection Steffen Eiden
2026-11-06 19:50 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 20/23] KVM: s390: arm64: Finalize page fault handling Steffen Eiden
2026-11-06 20:10 ` sashiko-bot [this message]
2026-11-06 16:07 ` [PATCH v3 21/23] KVM: s390: arm64: Implement SVE for arm guests Steffen Eiden
2026-11-06 20:24 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 22/23] KVM: s390: arm64: Promote PTRAUTH capability Steffen Eiden
2026-11-06 20:33 ` sashiko-bot
2026-11-06 16:07 ` [PATCH v3 23/23] s390: Report AEF features to sysfs Steffen Eiden
2026-11-06 20:43 ` sashiko-bot
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=sashiko-outbox-202185@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-s390@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=seiden@linux.ibm.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