Linux Watchdog driver development
 help / color / mirror / Atom feed
From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org,
	Xingyu Wu <xingyu.wu@starfivetech.com>,
	Ziv Xu <ziv.xu@starfivetech.com>
Subject: Re: [PATCH 5/5] watchdog: starfive-wdt: Drop runtime PM reference before registering watchdog
Date: Thu, 5 Nov 2026 15:15:10 +0000	[thread overview]
Message-ID: <auydfozcvsC4yjR-@google.com> (raw)
In-Reply-To: <20261104164445.3209560-6-linux@roeck-us.net>

On Wed, Nov 04, 2026 at 08:44:45AM -0800, Guenter Roeck wrote:
> In starfive_wdt_probe(), watchdog_register_device() is called before the
> probe-time runtime PM reference is released via pm_runtime_put_sync(), and
> any non-zero return value from pm_runtime_put_sync() is treated as a fatal
> probe error.
> 
> If userspace (such as udev or a watchdog daemon) opens /dev/watchdog
> immediately after watchdog_register_device() exposes the character device,
> starfive_wdt_pm_start() increments the runtime PM usage count. The
> subsequent pm_runtime_put_sync() in probe then decrements the usage count
> to 1 and returns -EAGAIN (it may also return 1, -EBUSY, or -EPERM in
> non-error idle conditions), causing starfive_wdt_probe() to unregister the
> working watchdog device and fail probe.
> 
> When early_enable is not set, no hardware registers are accessed after
> starfive_wdt_stop(). Release the probe-time runtime PM reference right
> after starfive_wdt_stop() and before watchdog_register_device(), without
> treating pm_runtime_put_sync() idle return codes as probe errors.
> 
> Fixes: 8bc22a2f1bf0 ("watchdog: starfive: Check pm_runtime_enabled() before decrementing usage counter")
> Cc: Xingyu Wu <xingyu.wu@starfivetech.com>
> Cc: Ziv Xu <ziv.xu@starfivetech.com>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>

The patch looks correct to me.

Reviewed-by: Tzung-Bi Shih <tzungbi@kernel.org>

> @@ -499,28 +499,25 @@ static int starfive_wdt_probe(struct platform_device *pdev)
>  		set_bit(WDOG_HW_RUNNING, &wdt->wdd.status);
>  	} else {
>  		starfive_wdt_stop(wdt);
> +		if (pm_runtime_enabled(&pdev->dev))
> +			pm_runtime_put_sync(&pdev->dev);
>  	}
>  
>  	ret = watchdog_register_device(&wdt->wdd);
> -	if (ret)
> -		goto err_exit;
> -
> -	if (!early_enable) {
> -		if (pm_runtime_enabled(&pdev->dev)) {
> -			ret = pm_runtime_put_sync(&pdev->dev);
> -			if (ret)
> -				goto err_unregister_wdt;
> +	if (ret) {
> +		if (watchdog_hw_running(&wdt->wdd)) {
> +			starfive_wdt_stop(wdt);
> +			if (pm_runtime_enabled(&pdev->dev))
> +				pm_runtime_put_sync(&pdev->dev);
>  		}
> +		if (!pm_runtime_enabled(&pdev->dev))
> +			starfive_wdt_disable_clock(wdt);
> +		goto err_disable_pm;
>  	}
>  
>  	return 0;
>  
> -err_unregister_wdt:
> -	watchdog_unregister_device(&wdt->wdd);
> -	goto err_disable_pm;
>  err_exit:
> -	if (watchdog_hw_running(&wdt->wdd))
> -		starfive_wdt_stop(wdt);
>  	if (pm_runtime_enabled(&pdev->dev))
>  		pm_runtime_put_sync(&pdev->dev);
>  	else

Would this improve readability?

	ret = watchdog_register_device(&wdt->wdd);
	if (ret) {
		if (early_enable) {
			starfive_wdt_stop(wdt);
			goto err_exit;
		} else {
			if (!pm_runtime_enabled(&pdev->dev))
				starfive_wdt_disable_clock(wdt);
		}
		goto err_disable_pm;
	}

  reply	other threads:[~2026-11-05 15:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 16:44 [PATCH 0/5] watchdog: starfive-wdt: Fix runtime PM and unclocked register access bugs Guenter Roeck
2026-11-04 16:44 ` [PATCH 1/5] watchdog: starfive-wdt: Drop runtime PM reference if starting watchdog fails Guenter Roeck
2026-11-05 13:46   ` Tzung-Bi Shih
2026-11-05 14:49     ` Guenter Roeck
2026-11-05 14:52       ` Guenter Roeck
2026-11-05 15:21         ` Tzung-Bi Shih
2026-11-04 16:44 ` [PATCH 2/5] watchdog: starfive-wdt: Balance pm_runtime_enable() on probe error paths Guenter Roeck
2026-11-05 13:46   ` Tzung-Bi Shih
2026-11-04 16:44 ` [PATCH 3/5] watchdog: starfive-wdt: Avoid unclocked register access in remove and PM paths Guenter Roeck
2026-11-04 17:02   ` sashiko-bot
2026-11-04 17:58     ` Guenter Roeck
2026-11-04 16:44 ` [PATCH 4/5] watchdog: starfive-wdt: Fix runtime PM usage count leaks in probe and remove Guenter Roeck
2026-11-05 15:15   ` Tzung-Bi Shih
2026-11-04 16:44 ` [PATCH 5/5] watchdog: starfive-wdt: Drop runtime PM reference before registering watchdog Guenter Roeck
2026-11-05 15:15   ` Tzung-Bi Shih [this message]
2026-11-06 14:22     ` Tzung-Bi Shih
2026-11-06 15:13       ` Guenter Roeck

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=auydfozcvsC4yjR-@google.com \
    --to=tzungbi@kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=xingyu.wu@starfivetech.com \
    --cc=ziv.xu@starfivetech.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