From: Thomas Gleixner <tglx@kernel.org>
To: Yingjun Ni <yingjun.ni@riscv-computing.com>,
anup@brainfault.org, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
yingjun.ni@riscv-computing.com
Subject: Re: [PATCH] irqchip/riscv-imsic: Fix irq migration failure issue when cpu hotplug.
Date: Tue, 03 Feb 2026 14:35:53 +0100 [thread overview]
Message-ID: <87ecn23q6e.ffs@tglx> (raw)
In-Reply-To: <20260203080256.9401-2-yingjun.ni@riscv-computing.com>
On Tue, Feb 03 2026 at 16:02, Yingjun Ni wrote:
> Add a null pointer check for irq_write_msi_msg to fix NULL pointer
> dereference issue when migrating irq.
>
> Modify the return value of imsic_irq_set_affinity to let the subdomain
> PCI-MSIX migrate the irq to a new cpu when cpu hotplug.
>
> Don't set vec->move_next in imsic_vector_move_update when the cpu is
> offline, because it will never be cleared.
You completely fail to explain the actual problem and the root
cause. See
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#changelog
> drivers/irqchip/irq-riscv-imsic-platform.c | 8 ++++++--
> drivers/irqchip/irq-riscv-imsic-state.c | 5 +++++
> 2 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/irqchip/irq-riscv-imsic-platform.c b/drivers/irqchip/irq-riscv-imsic-platform.c
> index 643c8e459611..131e4f2b5431 100644
> --- a/drivers/irqchip/irq-riscv-imsic-platform.c
> +++ b/drivers/irqchip/irq-riscv-imsic-platform.c
> @@ -93,9 +93,13 @@ static void imsic_irq_compose_msg(struct irq_data *d, struct msi_msg *msg)
> static void imsic_msi_update_msg(struct irq_data *d, struct imsic_vector *vec)
> {
> struct msi_msg msg = { };
> + struct irq_chip *irq_chip = irq_data_get_irq_chip(d);
> +
> + if (!irq_chip->irq_write_msi_msg)
> + return;
I have no idea how this ever worked. The irq_data pointer belongs to the
IMSIC base domain, which definitely does not have a irq_write_msi_msg()
callback and never can have one.
The write message callback is always implemented by the top most domain,
in this case the PCI/MSI[x] per device domain.
So this code is simply broken and your NULL pointer check just makes it
differently broken.
> imsic_irq_compose_vector_msg(vec, &msg);
> - irq_data_get_irq_chip(d)->irq_write_msi_msg(d, &msg);
> + irq_chip->irq_write_msi_msg(d, &msg);
> }
>
> static int imsic_irq_set_affinity(struct irq_data *d, const struct cpumask *mask_val,
> @@ -173,7 +177,7 @@ static int imsic_irq_set_affinity(struct irq_data *d, const struct cpumask *mask
> /* Move state of the old vector to the new vector */
> imsic_vector_move(old_vec, new_vec);
>
> - return IRQ_SET_MASK_OK_DONE;
> + return IRQ_SET_MASK_OK;
Have you actually looked at the consequences of this change?
> }
>
> static void imsic_irq_force_complete_move(struct irq_data *d)
> diff --git a/drivers/irqchip/irq-riscv-imsic-state.c b/drivers/irqchip/irq-riscv-imsic-state.c
> index b6cebfee9461..cd1bf9516878 100644
> --- a/drivers/irqchip/irq-riscv-imsic-state.c
> +++ b/drivers/irqchip/irq-riscv-imsic-state.c
> @@ -362,6 +362,10 @@ static bool imsic_vector_move_update(struct imsic_local_priv *lpriv,
> /* Update enable and move details */
> enabled = READ_ONCE(vec->enable);
> WRITE_ONCE(vec->enable, new_enable);
> +
> + if (!cpu_online(vec->cpu) && is_old_vec)
> + goto out;
This is definitely not correct as this should still cleanup software
state, no?
Thanks,
tglx
next prev parent reply other threads:[~2026-02-03 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 8:02 [PATCH] irqchip/riscv-imsic: Fix irq migration failure issue when cpu hotplug Yingjun Ni
2026-02-03 13:35 ` Thomas Gleixner [this message]
2026-02-03 17:09 ` Anup Patel
2026-02-03 18:28 ` Thomas Gleixner
2026-02-03 21:05 ` [PATCH] irqchip/msi-lib: Refuse initialization when irq_write_msi_msg() is missing Thomas Gleixner
2026-02-24 7:20 ` [tip: irq/msi] " tip-bot2 for Thomas Gleixner
2026-02-04 1:59 ` [PATCH] irqchip/riscv-imsic: Fix irq migration failure issue when cpu hotplug Yingjun Ni
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=87ecn23q6e.ffs@tglx \
--to=tglx@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=yingjun.ni@riscv-computing.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