From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: Yanfei Xu <yanfei.xu@bytedance.com>,
zhaotianrui@loongson.cn, maobibo@loongson.cn,
chenhuacai@kernel.org, maddy@linux.ibm.com, npiggin@gmail.com,
sashiko-reviews@lists.linux.dev, seanjc@google.com,
pbonzini@redhat.com
Cc: kvm@vger.kernel.org, loongarch@lists.linux.dev,
linuxppc-dev@lists.ozlabs.org, caixiangfeng@bytedance.com,
fangying.tommy@bytedance.com, isyanfei.xu@gmail.com,
Sashiko <sashiko-bot@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] KVM: Validate irqchip index for LoongArch and PowerPC
Date: Tue, 26 May 2026 12:02:58 +0530 [thread overview]
Message-ID: <76f82194-9afb-4dfe-ad96-ae338c7db61d@linux.ibm.com> (raw)
In-Reply-To: <20260525070154.495455-1-yanfei.xu@bytedance.com>
+ cc: stable@vger.kernel.org
On 25/05/26 12:31 pm, Yanfei Xu wrote:
> Sashiko reported that irqchip index is not validated for LoongArch and
> PowerPC. Add validation and reject out-of-range irqchip indexes to avoid
> indexing past the routing table's chip array.
>
> Fixes: de9ba2f36368 ("KVM: PPC: Support irq routing and irqfd for in-kernel MPIC")
> Fixes: 1928254c5ccb ("LoongArch: KVM: Add irqfd support")
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Closes: https://lore.kernel.org/kvm/20260525051714.485D51F000E9@smtp.kernel.org/
> Signed-off-by: Yanfei Xu <yanfei.xu@bytedance.com>
> ---
> arch/loongarch/kvm/irqfd.c | 3 ++-
> arch/powerpc/kvm/mpic.c | 3 ++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/loongarch/kvm/irqfd.c b/arch/loongarch/kvm/irqfd.c
> index f4f953b22419..40ed1081c4b6 100644
> --- a/arch/loongarch/kvm/irqfd.c
> +++ b/arch/loongarch/kvm/irqfd.c
> @@ -51,7 +51,8 @@ int kvm_set_routing_entry(struct kvm *kvm,
> e->irqchip.irqchip = ue->u.irqchip.irqchip;
> e->irqchip.pin = ue->u.irqchip.pin;
>
> - if (e->irqchip.pin >= KVM_IRQCHIP_NUM_PINS)
> + if (e->irqchip.pin >= KVM_IRQCHIP_NUM_PINS ||
> + e->irqchip.irqchip >= KVM_NR_IRQCHIPS)
> return -EINVAL;
>
> return 0;
> diff --git a/arch/powerpc/kvm/mpic.c b/arch/powerpc/kvm/mpic.c
> index 3070f36d9fb8..fb5f9e65e02e 100644
> --- a/arch/powerpc/kvm/mpic.c
> +++ b/arch/powerpc/kvm/mpic.c
> @@ -1833,7 +1833,8 @@ int kvm_set_routing_entry(struct kvm *kvm,
> e->set = mpic_set_irq;
> e->irqchip.irqchip = ue->u.irqchip.irqchip;
> e->irqchip.pin = ue->u.irqchip.pin;
> - if (e->irqchip.pin >= KVM_IRQCHIP_NUM_PINS)
> + if (e->irqchip.pin >= KVM_IRQCHIP_NUM_PINS ||
> + e->irqchip.irqchip >= KVM_NR_IRQCHIPS)
Reviewed-by: Harsh Prateek Bora <harshpb@linux.ibm.com> # PPC KVM
> goto out;
> break;
> case KVM_IRQ_ROUTING_MSI:
next prev parent reply other threads:[~2026-05-26 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 7:01 [PATCH] KVM: Validate irqchip index for LoongArch and PowerPC Yanfei Xu
2026-05-26 6:32 ` Harsh Prateek Bora [this message]
2026-05-26 7:04 ` Bibo Mao
2026-05-29 22:51 ` Sean Christopherson
2026-05-31 14:02 ` Yanfei Xu
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=76f82194-9afb-4dfe-ad96-ae338c7db61d@linux.ibm.com \
--to=harshpb@linux.ibm.com \
--cc=caixiangfeng@bytedance.com \
--cc=chenhuacai@kernel.org \
--cc=fangying.tommy@bytedance.com \
--cc=isyanfei.xu@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=maobibo@loongson.cn \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=yanfei.xu@bytedance.com \
--cc=zhaotianrui@loongson.cn \
/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