From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Chen Ni <nichen@iscas.ac.cn>, qiang.zhao@nxp.com
Cc: linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: fsl: qe: qe_ports_ic: Consolidate chained IRQ handler install/remove
Date: Mon, 19 Jan 2026 08:00:01 +0100 [thread overview]
Message-ID: <3860577c-2cef-4e10-9cc1-33246d261a8b@kernel.org> (raw)
In-Reply-To: <20260119055715.889001-1-nichen@iscas.ac.cn>
Le 19/01/2026 à 06:57, Chen Ni a écrit :
> [Vous ne recevez pas souvent de courriers de nichen@iscas.ac.cn. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ]
>
> The driver currently sets the handler data and the chained handler in
> two separate steps. This creates a theoretical race window where an
> interrupt could fire after the handler is set but before the data is
> assigned, leading to a NULL pointer dereference.
I don't understand what you mean, how can this happen ?
irq_set_handler_data() is called _before_ irq_set_chained_handler(), so
how could an interrupt fire _before_ the data is assigned ?
>
> Replace the two calls with irq_set_chained_handler_and_data() to set
> both the handler and its data atomically under the irq_desc->lock.
>
> Signed-off-by: Chen Ni <nichen@iscas.ac.cn>
> ---
> drivers/soc/fsl/qe/qe_ports_ic.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/soc/fsl/qe/qe_ports_ic.c b/drivers/soc/fsl/qe/qe_ports_ic.c
> index 61dd09fec6f6..8e2107e2cde5 100644
> --- a/drivers/soc/fsl/qe/qe_ports_ic.c
> +++ b/drivers/soc/fsl/qe/qe_ports_ic.c
> @@ -114,8 +114,7 @@ static int qepic_probe(struct platform_device *pdev)
> if (!data->host)
> return -ENODEV;
>
> - irq_set_handler_data(irq, data);
> - irq_set_chained_handler(irq, qepic_cascade);
> + irq_set_chained_handler_and_data(irq, qepic_cascade, data);
>
> return 0;
> }
> --
> 2.25.1
>
next prev parent reply other threads:[~2026-01-19 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 5:57 [PATCH] soc: fsl: qe: qe_ports_ic: Consolidate chained IRQ handler install/remove Chen Ni
2026-01-19 7:00 ` Christophe Leroy (CS GROUP) [this message]
2026-01-28 11:01 ` Christophe Leroy (CS GROUP)
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=3860577c-2cef-4e10-9cc1-33246d261a8b@kernel.org \
--to=chleroy@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nichen@iscas.ac.cn \
--cc=qiang.zhao@nxp.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