From: sashiko-bot@kernel.org
To: "Sean Christopherson" <seanjc@google.com>
Cc: kvmarm@lists.linux.dev, "Oliver Upton" <oupton@kernel.org>,
"Marc Zyngier" <maz@kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH v8 11/20] KVM: selftests: Verify interrupts are received when IRQ affinity changes in IRQ test
Date: Fri, 26 Jun 2026 21:46:36 +0000 [thread overview]
Message-ID: <20260626214636.DD9491F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260626213534.3866178-12-seanjc@google.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The IRQ affinity logic incorrectly assumes that CPU IDs are contiguous and zero-indexed up to `get_nprocs() - 1`, which will cause spurious test crashes on systems with sparse CPU topologies or offline CPUs.
--
commit 907b9a0cf2f427a532d2facb5d6393850a4b6083
Author: David Matlack <dmatlack@google.com>
KVM: selftests: Verify interrupts are received when IRQ affinity changes in IRQ test
This commit extends the KVM eventfd IRQ selftest with a '-a' flag. This flag
randomly affinitizes the device's host IRQ to different physical CPUs to
stress KVM's interrupt routing logic while affinity changes dynamically.
> diff --git a/tools/testing/selftests/kvm/irq_test.c b/tools/testing/selftests/kvm/irq_test.c
> index 70b2c9cac2790..fd386e3e9ac3e 100644
> --- a/tools/testing/selftests/kvm/irq_test.c
> +++ b/tools/testing/selftests/kvm/irq_test.c
[ ... ]
> @@ -228,6 +239,11 @@ int main(int argc, char **argv)
>
> kvm_route_msi(vm, gsi, vcpu, vector);
>
> + if (irq_affinity) {
> + irq_cpu = kvm_random_u64(&kvm_rng) % get_nprocs();
> + proc_irq_set_smp_affinity(irq, irq_cpu);
[Severity: Medium]
Will this cause spurious test crashes on systems with non-contiguous CPU IDs
or offline CPUs?
Since get_nprocs() returns the count of currently online processors, using it
with a modulo operation in main() assumes that the online CPU IDs are
contiguous and start from 0. On a system where CPUs are offline or the
numbering is sparse (for example, if only CPUs 0 and 2 are online,
get_nprocs() returns 2, and the modulo yields 0 or 1), this could select an
offline or non-existent CPU ID.
Attempting to write an invalid CPU ID to /proc/irq/<irq>/smp_affinity_list
via proc_irq_set_smp_affinity() would then fail with -EINVAL and erroneously
crash the test.
> + }
> +
> for (j = 0; j < nr_vcpus; j++)
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260626213534.3866178-1-seanjc@google.com?part=11
next prev parent reply other threads:[~2026-06-26 21:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 21:35 [PATCH v8 00/20] KVM: selftests: Add eventfd+VFIO IRQ test Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 01/20] KVM: selftests: Build and link selftests/vfio/lib into KVM selftests Sean Christopherson
2026-06-26 21:44 ` sashiko-bot
2026-06-26 21:35 ` [PATCH v8 02/20] KVM: selftests: Add macros to read/write+sync to/from guest memory Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 03/20] KVM: selftests: Rename guest_rng to kvm_rng Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 04/20] KVM: selftests: Initialize the default/global pRNG during kvm_selftest_init() Sean Christopherson
2026-06-26 21:48 ` sashiko-bot
2026-06-26 21:59 ` Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 05/20] KVM: selftests: Seed libc's RNG before using it to generate a seed for KVM's pRNG Sean Christopherson
2026-06-26 21:43 ` sashiko-bot
2026-06-26 21:35 ` [PATCH v8 06/20] KVM: selftests: Add helper to generate random u64 in range [min,max] Sean Christopherson
2026-06-26 21:44 ` sashiko-bot
2026-06-26 21:35 ` [PATCH v8 07/20] KVM: selftests: Add an irqfd send+receive (and later IRQ bypass) test Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 08/20] KVM: selftests: Add helper to get host IRQ from device MSI-X for IRQ bypass test Sean Christopherson
2026-06-26 21:42 ` sashiko-bot
2026-06-26 21:35 ` [PATCH v8 09/20] KVM: selftests: Add VFIO device support to eventfd IRQ test Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 10/20] KVM: selftests: Add a helper to set proc IRQ affinity for " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 11/20] KVM: selftests: Verify interrupts are received when IRQ affinity changes in " Sean Christopherson
2026-06-26 21:46 ` sashiko-bot [this message]
2026-06-26 21:35 ` [PATCH v8 12/20] KVM: selftests: Add option to set empty routing between IRQs in eventfd " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 13/20] KVM: selftests: Make number of IRQs configurable in " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 14/20] KVM: selftests: Verify non-postable IRQ remapping " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 15/20] KVM: selftests: Add kvm_gettid() wrapper and convert users Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 16/20] KVM: selftests: Add kvm_sched_getaffinity() " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 17/20] KVM: selftests: Add a utility to pin a task to a random CPU, given a CPU set Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 18/20] KVM: selftests: Verify vCPU migration during IRQ delivery in IRQ test Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 19/20] KVM: selftests: Make number of vCPUs configurable " Sean Christopherson
2026-06-26 21:35 ` [PATCH v8 20/20] KVM: selftests: Add xAPIC support in eventfd " Sean Christopherson
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=20260626214636.DD9491F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=seanjc@google.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