Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Jiangshan Yi <yijiangshan@kylinos.cn>
Cc: lpieralisi@kernel.org, tglx@kernel.org, radu@rendec.net,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, 13667453960@163.com
Subject: Re: [PATCH] irqchip/gic-v5: Install root IRQ handler last in gicv5_init_common()
Date: Wed, 02 Sep 2026 16:54:41 +0100	[thread overview]
Message-ID: <87fqzrmywu.wl-maz@kernel.org> (raw)
In-Reply-To: <20260902143255.182786-1-yijiangshan@kylinos.cn>

On Wed, 02 Sep 2026 15:32:55 +0100,
Jiangshan Yi <yijiangshan@kylinos.cn> wrote:
> 
> set_handle_irq() is irreversible: once installed, handle_arch_irq
> points at gicv5_handle_irq, which dereferences the PPI/SPI/LPI
> irqdomains.  If gicv5_irs_enable() fails afterwards, the error path
> calls gicv5_free_domains() while handle_arch_irq still references
> those domains.

I don't think that's a massive problem. If you can't enable the IRS,
you can't do much at all. Your system is already completely dead.

>
> Move set_handle_irq() after gicv5_irs_enable() so the handler is
> only installed once all fallible steps have succeeded.  Drop the
> no-op set_handle_irq(NULL) in the error path, which never worked
> because set_handle_irq() returns -EBUSY once a handler is set.

That is a reasonable cleanup.

>
> Fixes: 183750b276c2 ("irqchip/gic-v5: Fix gicv5_init_common() error paths")
> Signed-off-by: Jiangshan Yi <yijiangshan@kylinos.cn>
> ---
>  drivers/irqchip/irq-gic-v5.c | 8 +++-----
>  1 file changed, 3 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/irqchip/irq-gic-v5.c b/drivers/irqchip/irq-gic-v5.c
> index ac2d423b1723..37184942dc11 100644
> --- a/drivers/irqchip/irq-gic-v5.c
> +++ b/drivers/irqchip/irq-gic-v5.c
> @@ -1166,21 +1166,19 @@ static int __init gicv5_init_common(struct fwnode_handle *parent_domain)
>  	if (ret)
>  		goto out_int;
>  
> -	ret = set_handle_irq(gicv5_handle_irq);
> +	ret = gicv5_irs_enable();
>  	if (ret)
>  		goto out_int;
>  
> -	ret = gicv5_irs_enable();
> +	ret = set_handle_irq(gicv5_handle_irq);
>  	if (ret)
> -		goto out_handle;
> +		goto out_int;

Under which circumstance can this fail? There should be none. So if
this ever returns an error, we should immediately stop with a panic.
No need to clean anything up, just die on the spot.

>  
>  	gicv5_smp_init();
>  
>  	gicv5_irs_its_probe();
>  	return 0;
>  
> -out_handle:
> -	set_handle_irq(NULL);
>  out_int:
>  	gicv5_cpu_disable_interrupts();
>  	gicv5_free_domains();

Thanks,

	M.

-- 
Jazz isn't dead. It just smells funny.


  reply	other threads:[~2026-09-02 15:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 14:32 [PATCH] irqchip/gic-v5: Install root IRQ handler last in gicv5_init_common() Jiangshan Yi
2026-09-02 15:54 ` Marc Zyngier [this message]
2026-09-03 10:33   ` Jiangshan Yi

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=87fqzrmywu.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=13667453960@163.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=radu@rendec.net \
    --cc=tglx@kernel.org \
    --cc=yijiangshan@kylinos.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