From: Rodolfo Giometti <giometti@enneenne.com>
To: Eliav Farber <farbere@amazon.com>
Cc: jonnyc@amazon.com, gregkh@linuxfoundation.org,
mschmidt@redhat.com, calvin@wbinvd.org,
u.kleine-koenig@pengutronix.de, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pps: clients: gpio: fix interrupt handling order in remove path
Date: Tue, 27 May 2025 10:00:50 +0200 [thread overview]
Message-ID: <64886460-b8b2-4ad7-bf87-b3b98971e355@enneenne.com> (raw)
In-Reply-To: <20250527053355.37185-1-farbere@amazon.com>
On 27/05/25 07:33, Eliav Farber wrote:
> The interrupt handler in pps_gpio_probe() is registered after calling
> pps_register_source() using devm_request_irq(). However, in the
> corresponding remove function, pps_unregister_source() is called before
> the IRQ is freed, since devm-managed resources are released after the
> remove function completes.
>
> This creates a potential race condition where an interrupt may occur
> after the PPS source is unregistered but before the handler is removed,
> possibly leading to a kernel panic.
>
> To prevent this, switch from devm-managed IRQ registration to manual
> management by using request_irq() and calling free_irq() explicitly in
> the remove path before unregistering the PPS source. This ensures the
> interrupt handler is safely removed before deactivating the PPS source.
>
> Signed-off-by: Eliav Farber <farbere@amazon.com>
> ---
> drivers/pps/clients/pps-gpio.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pps/clients/pps-gpio.c b/drivers/pps/clients/pps-gpio.c
> index 374ceefd6f2a..2866636b0554 100644
> --- a/drivers/pps/clients/pps-gpio.c
> +++ b/drivers/pps/clients/pps-gpio.c
> @@ -210,8 +210,8 @@ static int pps_gpio_probe(struct platform_device *pdev)
> }
>
> /* register IRQ interrupt handler */
> - ret = devm_request_irq(dev, data->irq, pps_gpio_irq_handler,
> - get_irqf_trigger_flags(data), data->info.name, data);
> + ret = request_irq(data->irq, pps_gpio_irq_handler,
> + get_irqf_trigger_flags(data), data->info.name, data);
> if (ret) {
> pps_unregister_source(data->pps);
> dev_err(dev, "failed to acquire IRQ %d\n", data->irq);
> @@ -228,6 +228,7 @@ static void pps_gpio_remove(struct platform_device *pdev)
> {
> struct pps_gpio_device_data *data = platform_get_drvdata(pdev);
>
> + free_irq(data->irq, data);
Why not just use devm_free_irq()?
> pps_unregister_source(data->pps);
> timer_delete_sync(&data->echo_timer);
> /* reset echo pin in any case */
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming
next prev parent reply other threads:[~2025-05-27 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 5:33 [PATCH] pps: clients: gpio: fix interrupt handling order in remove path Eliav Farber
2025-05-27 8:00 ` Rodolfo Giometti [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-27 9:11 Farber, Eliav
2025-05-27 10:19 ` Rodolfo Giometti
2025-05-27 10:24 ` gregkh
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=64886460-b8b2-4ad7-bf87-b3b98971e355@enneenne.com \
--to=giometti@enneenne.com \
--cc=calvin@wbinvd.org \
--cc=farbere@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonnyc@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
/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