Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, gregkh@linuxfoundation.org
Cc: Sasha Levin <sashal@kernel.org>, Xie Bo <xb@ultrarisc.com>,
	Anup Patel <anup@brainfault.org>
Subject: Re: [PATCH 6.12.y] RISC-V: KVM: Serialize virtual interrupt pending state updates
Date: Mon, 27 Jul 2026 18:19:43 -0400	[thread overview]
Message-ID: <20260727202413.stable-0010@kernel.org> (raw)
In-Reply-To: <20260727023348.2173961-1-xb@ultrarisc.com>

On Mon, Jul 27, 2026 at 10:33:48AM +0800, Xie Bo wrote:
>@@ -174,6 +187,9 @@ int kvm_riscv_vcpu_aia_get_csr(struct kvm_vcpu *vcpu,
> 			       unsigned long *out_val)
> {
> 	struct kvm_vcpu_aia_csr *csr = &vcpu->arch.aia_context.guest_csr;
>+#ifdef CONFIG_32BIT
>+	unsigned long flags;
>+#endif

This declaration landed in kvm_riscv_vcpu_aia_get_csr(), but the use site
is in kvm_riscv_vcpu_aia_set_csr():

>@@ -198,8 +214,12 @@ int kvm_riscv_vcpu_aia_set_csr(struct kvm_vcpu *vcpu,
>+		if (reg_num == KVM_REG_RISCV_CSR_AIA_REG(siph)) {
>+			raw_spin_lock_irqsave(&vcpu->arch.irqs_pending_lock, flags);

So on CONFIG_32BIT builds 'flags' is undeclared here and rv32 KVM fails to
build (KVM on riscv only depends on RISCV_SBI && MMU, so this is a real
configuration), plus the declaration in the getter is unused. The two
function prologues are identical, which is presumably how the hunk
anchored in the wrong one.

Could you send a v2 with the declaration moved into
kvm_riscv_vcpu_aia_set_csr()? Everything else in the patch matches
upstream d024a0a7879e ("RISC-V: KVM: Serialize virtual interrupt pending
state updates").

I've queued your 6.18.y patch. I'm holding the 6.6.y one until the
corrected 6.12.y lands, so that 6.6 doesn't ship a fix that 6.12 is
missing - both will go in together.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-07-27 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-25  6:52 FAILED: patch "[PATCH] RISC-V: KVM: Serialize virtual interrupt pending state" failed to apply to 6.12-stable tree gregkh
2026-07-27  2:33 ` [PATCH 6.12.y] RISC-V: KVM: Serialize virtual interrupt pending state updates Xie Bo
2026-07-27 22:19   ` Sasha Levin [this message]
2026-07-28  1:35     ` [PATCH 6.12.y v2] " Xie Bo
2026-07-28 16:09       ` Sasha Levin

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=20260727202413.stable-0010@kernel.org \
    --to=sashal@kernel.org \
    --cc=anup@brainfault.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=xb@ultrarisc.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