Re: [PATCH] watchdog: msc313e: Fix premature reset during timeout update

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] Incomplete race condition fix leading to premature system reset during watchdog timeout update.
--

commit 7f35d2e3193543673ce5c7858773cd48582d5c52
Author: Tzung-Bi Shih <tzungbi@kernel.org>

watchdog: msc313e: Fix premature reset during timeout update

Updating the 32-bit hardware timeout requires writing to two 16-bit
registers sequentially. Clear the watchdog counter before updating the
registers to prevent the timer from timing out prematurely.

> diff --git a/drivers/watchdog/msc313e_wdt.c b/drivers/watchdog/msc313e_wdt.c
> index 4a5cce2a16b18..a743087e922d5 100644
> --- a/drivers/watchdog/msc313e_wdt.c
> +++ b/drivers/watchdog/msc313e_wdt.c
> @@ -46,6 +46,9 @@ static void msc313e_wdt_set_hw_timeout(struct msc313e_wdt_priv *priv,
>  {
>  	u32 t = timeout * clk_get_rate(priv->clk);
>  
> +	/* Clear before to prevent premature reset during non-atomic updates. */
> +	writew(1, priv->base + REG_WDT_CLR);
> +
>  	writew(t & 0xffff, priv->base + REG_WDT_MAX_PRD_L);
>  	writew((t >> 16) & 0xffff, priv->base + REG_WDT_MAX_PRD_H);

[Severity: High]
This is a pre-existing issue, but does this non-atomic update still leave a
race condition window?

If a preemption or interrupt occurs between these two writes in
msc313e_wdt_set_hw_timeout(), the active threshold becomes a hybrid of the
old high bits and the new low bits.

Since the counter was just cleared to 0 immediately prior to this, if the
old high bits are 0 and the new low bits are small, the intermediate
threshold will be very low.

Could the counter reach this small intermediate threshold during the
preemption window and still trigger a premature hardware reset?

>  	writew(1, priv->base + REG_WDT_CLR);
>  }

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260913065126.8350-1-tzungbi@kernel.org?part=1