From: sashiko-bot@kernel.org
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: imx@lists.linux.dev, linux-gpio@vger.kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v5 01/13] gpio: mxc: fix race between chained IRQ handler install and probe completion
Date: Fri, 09 Oct 2026 18:22:51 +0000 [thread overview]
Message-ID: <sashiko-outbox-165937@kernel.org> (raw)
In-Reply-To: <20261010-gpio-mxc-cleanup-v5-1-1e59e6ddfa00@nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] gpio: mxc: lockless mxc_gpio_ports list race with shared IRQ handler
--
commit cfebba0884b34920e4ae09750fb2bbf30c42ba32
Author: Peng Fan <peng.fan@nxp.com>
gpio: mxc: fix race between chained IRQ handler install and probe completion
This commit delays installing the chained IRQ handler in mxc_gpio_probe()
until after the generic IRQ chip, port list entry, and IRQ domain are fully
setup. This ensures the handler does not execute while data structures are
incomplete and prevents leaving a dangling handler if probe fails.
> diff --git a/drivers/gpio/gpio-mxc.c b/drivers/gpio/gpio-mxc.c
> index 7e2690d92df6f..e05f276a50e8d 100644
> --- a/drivers/gpio/gpio-mxc.c
> +++ b/drivers/gpio/gpio-mxc.c
[ ... ]
> @@ -525,6 +523,8 @@ static int mxc_gpio_probe(struct platform_device *pdev)
>
> list_add_tail(&port->node, &mxc_gpio_ports);
>
> + mxc_update_irq_chained_handler(port, true);
> +
[Severity: High]
Does this still leave a race condition for shared IRQs?
On i.MX21/i.MX27, all GPIO ports share the same parent IRQ. When the first
port probes, it registers mx2_gpio_irq_handler for the shared IRQ, enabling
it.
When the second port probes, it calls list_add_tail() to add itself to
mxc_gpio_ports. If an interrupt arrives concurrently on the already-active
first port, mx2_gpio_irq_handler() iterates over mxc_gpio_ports locklessly in
hardirq context.
Since list_add_tail() uses non-atomic pointer updates without compiler or
memory barriers (unlike list_add_rcu), could the active IRQ handler traverse a
corrupted list if it preempts the update, dereferencing invalid memory?
While moving the handler installation prevents races for the first port, for
shared IRQs the handler is already live. This leaves the lockless list
mutation race unresolved.
> platform_set_drvdata(pdev, port);
> pm_runtime_put_autosuspend(&pdev->dev);
>
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261010-gpio-mxc-cleanup-v5-0-1e59e6ddfa00@nxp.com?part=1
next prev parent reply other threads:[~2026-10-09 18:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 18:05 [PATCH v5 00/13] gpio: mxc: bug fixes and probe cleanup Peng Fan (OSS)
2026-10-09 18:05 ` [PATCH v5 01/13] gpio: mxc: fix race between chained IRQ handler install and probe completion Peng Fan (OSS)
2026-10-09 18:22 ` sashiko-bot [this message]
2026-10-09 18:29 ` Frank Li
2026-10-09 18:05 ` [PATCH v5 02/13] gpio: mxc: fix both_edges bit operations Peng Fan (OSS)
2026-10-09 18:33 ` Frank Li
2026-10-09 18:05 ` [PATCH v5 03/13] gpio: mxc: fix wakeup_pads " Peng Fan (OSS)
2026-10-09 18:35 ` Frank Li
2026-10-09 18:05 ` [PATCH v5 04/13] gpio: mxc: simplify gpio_set_wake_irq Peng Fan (OSS)
2026-10-09 18:39 ` Frank Li
2026-10-09 18:05 ` [PATCH v5 05/13] gpio: mxc: use for_each_set_bit() to iterate wakeup pads Peng Fan (OSS)
2026-10-09 18:05 ` [PATCH v5 06/13] gpio: mxc: replace of_device_is_compatible() with hwdata flags Peng Fan (OSS)
2026-10-09 18:05 ` [PATCH v5 07/13] gpio: mxc: convert pad wakeup compatible checks to " Peng Fan (OSS)
2026-10-09 18:45 ` Frank Li
2026-10-09 18:05 ` [PATCH v5 08/13] gpio: mxc: use local dev variable Peng Fan (OSS)
2026-10-09 18:05 ` [PATCH v5 09/13] gpio: mxc: use cleanup guard for pm_runtime_get_noresume() balance Peng Fan (OSS)
2026-10-09 18:19 ` sashiko-bot
2026-10-09 18:51 ` Frank Li
2026-10-09 18:05 ` [PATCH v5 10/13] gpio: mxc: convert probe error handling to devres Peng Fan (OSS)
2026-10-09 18:23 ` sashiko-bot
2026-10-09 18:53 ` Frank Li
2026-10-09 18:05 ` [PATCH v5 11/13] gpio: mxc: switch probe error paths to dev_err_probe() Peng Fan (OSS)
2026-10-09 18:21 ` sashiko-bot
2026-10-09 18:55 ` Frank Li
2026-10-09 18:05 ` [PATCH v5 12/13] gpio: mxc: introduce MXC_ICR macros and use field_prep/field_get Peng Fan (OSS)
2026-10-09 18:58 ` Frank Li
2026-10-09 18:05 ` [PATCH v5 13/13] gpio: mxc: use BIT() macro for single-bit operations Peng Fan (OSS)
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=sashiko-outbox-165937@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=imx@lists.linux.dev \
--cc=linux-gpio@vger.kernel.org \
--cc=peng.fan@oss.nxp.com \
--cc=sashiko-reviews@lists.linux.dev \
/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