From: Sean Christopherson <seanjc@google.com>
To: Yanfei Xu <yanfei.xu@bytedance.com>
Cc: zhaotianrui@loongson.cn, maobibo@loongson.cn,
chenhuacai@kernel.org, maddy@linux.ibm.com, npiggin@gmail.com,
sashiko-reviews@lists.linux.dev, pbonzini@redhat.com,
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>
Subject: Re: [PATCH] KVM: Validate irqchip index for LoongArch and PowerPC
Date: Fri, 29 May 2026 15:51:34 -0700 [thread overview]
Message-ID: <ahoYdrs9dVzp6Ps6@google.com> (raw)
In-Reply-To: <20260525070154.495455-1-yanfei.xu@bytedance.com>
On Mon, May 25, 2026, 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.
Can you split this into two patches, and send a v2? I suspect the reason no one
has picked this up is because it straddles two completely different (sub)subsystems.
That would also make it easier to get the fixes backported to stable trees. PPC
has been around a lot longer than LoongArch, so I assume the PPC fix will need to
go further back in time.
Thanks!
next prev parent reply other threads:[~2026-05-29 22:51 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
2026-05-26 7:04 ` Bibo Mao
2026-05-29 22:51 ` Sean Christopherson [this message]
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=ahoYdrs9dVzp6Ps6@google.com \
--to=seanjc@google.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=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