From: Paul Walmsley <pjw@kernel.org>
To: Osama Abdelkader <osama.abdelkader@gmail.com>
Cc: Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Thomas Gleixner <tglx@kernel.org>,
Vladimir Kondratiev <vladimir.kondratiev@mobileye.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated
Date: Thu, 2 Apr 2026 16:11:59 -0600 (MDT) [thread overview]
Message-ID: <dba67dea-baec-ab20-09b2-e007ee6bb88c@kernel.org> (raw)
In-Reply-To: <20260326232335.60353-1-osama.abdelkader@gmail.com>
Hi,
On Fri, 27 Mar 2026, Osama Abdelkader wrote:
> init_irq_stacks() and init_irq_scs() may fail when arch_alloc_vmap_stack
> or scs_alloc return NULL. Return -ENOMEM from both and call panic() once
> from init_IRQ(), covering per-CPU IRQ stacks and shadow IRQ stacks
> consistently.
>
> Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
This patch appears to be written with AI assistance. If so, it should be
noted in the description. Please see
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-assistants.rst
> ---
> arch/riscv/kernel/irq.c | 43 ++++++++++++++++++++++++++++++-----------
> 1 file changed, 32 insertions(+), 11 deletions(-)
>
> diff --git a/arch/riscv/kernel/irq.c b/arch/riscv/kernel/irq.c
> index b6af20bc300f..43392276f7f8 100644
> --- a/arch/riscv/kernel/irq.c
> +++ b/arch/riscv/kernel/irq.c
> @@ -5,6 +5,7 @@
> * Copyright (C) 2018 Christoph Hellwig
> */
>
> +#include <linux/errno.h>
> #include <linux/interrupt.h>
> #include <linux/irqchip.h>
> #include <linux/irqdomain.h>
> @@ -75,41 +76,53 @@ DECLARE_PER_CPU(ulong *, irq_shadow_call_stack_ptr);
> DEFINE_PER_CPU(ulong *, irq_shadow_call_stack_ptr);
> #endif
>
> -static void init_irq_scs(void)
> +static int __init init_irq_scs(void)
> {
> int cpu;
> + void *s;
>
> if (!scs_is_enabled())
> - return;
> + return 0;
>
> - for_each_possible_cpu(cpu)
> - per_cpu(irq_shadow_call_stack_ptr, cpu) =
> - scs_alloc(cpu_to_node(cpu));
> + for_each_possible_cpu(cpu) {
> + s = scs_alloc(cpu_to_node(cpu));
> + if (!s)
> + return -ENOMEM;
I don't see why this bothers to return an error value if the sole caller
is just going to panic. Best to panic here. Then no one reviewing this
patch needs to be concerned about memory leaks.
> + per_cpu(irq_shadow_call_stack_ptr, cpu) = s;
> + }
> +
> + return 0;
> }
>
> DEFINE_PER_CPU(ulong *, irq_stack_ptr);
>
> #ifdef CONFIG_VMAP_STACK
> -static void init_irq_stacks(void)
> +static int __init init_irq_stacks(void)
> {
> int cpu;
> ulong *p;
>
> for_each_possible_cpu(cpu) {
> p = arch_alloc_vmap_stack(IRQ_STACK_SIZE, cpu_to_node(cpu));
> + if (!p)
> + return -ENOMEM;
Same comment as the above.
> per_cpu(irq_stack_ptr, cpu) = p;
> }
> +
> + return 0;
> }
> #else
> /* irq stack only needs to be 16 byte aligned - not IRQ_STACK_SIZE aligned. */
> DEFINE_PER_CPU_ALIGNED(ulong [IRQ_STACK_SIZE/sizeof(ulong)], irq_stack);
>
> -static void init_irq_stacks(void)
> +static int __init init_irq_stacks(void)
> {
> int cpu;
>
> for_each_possible_cpu(cpu)
> per_cpu(irq_stack_ptr, cpu) = per_cpu(irq_stack, cpu);
> +
> + return 0;
Why?
> }
> #endif /* CONFIG_VMAP_STACK */
>
> @@ -129,8 +142,15 @@ void do_softirq_own_stack(void)
> #endif /* CONFIG_SOFTIRQ_ON_OWN_STACK */
>
> #else
> -static void init_irq_scs(void) {}
> -static void init_irq_stacks(void) {}
> +static int __init init_irq_scs(void)
> +{
> + return 0;
> +}
> +
> +static int __init init_irq_stacks(void)
> +{
> + return 0;
> +}
> #endif /* CONFIG_IRQ_STACKS */
>
> int arch_show_interrupts(struct seq_file *p, int prec)
> @@ -141,8 +161,9 @@ int arch_show_interrupts(struct seq_file *p, int prec)
>
> void __init init_IRQ(void)
> {
> - init_irq_scs();
> - init_irq_stacks();
> + if (init_irq_stacks() || init_irq_scs())
> + panic("Failed to allocate IRQ stack resources\n");
Any reason why the initialization order is reversed?
> +
> irqchip_init();
> if (!handle_arch_irq)
> panic("No interrupt controller found.");
> --
> 2.43.0
- Paul
next prev parent reply other threads:[~2026-04-02 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 23:23 [PATCH] riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated Osama Abdelkader
2026-04-02 22:11 ` Paul Walmsley [this message]
2026-04-03 14:27 ` Osama Abdelkader
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=dba67dea-baec-ab20-09b2-e007ee6bb88c@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=osama.abdelkader@gmail.com \
--cc=palmer@dabbelt.com \
--cc=tglx@kernel.org \
--cc=vladimir.kondratiev@mobileye.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