From: Stefan Eichenberger <eichest@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>
Subject: Re: [PATCH] watchdog: imx_sc_wdt: fix pretimeout
Date: Mon, 5 Apr 2021 19:43:52 +0200 [thread overview]
Message-ID: <20210405174352.GA395591@eichest-laptop> (raw)
In-Reply-To: <2580102e-4459-c55e-0aab-2882af8e9ae7@roeck-us.net>
Hi Guenter,
On Mon, Apr 05, 2021 at 07:42:20AM -0700, Guenter Roeck wrote:
> On 4/5/21 5:59 AM, eichest@gmail.com wrote:
> > From: Stefan Eichenberger <eichest@gmail.com>
> >
> > If the WDIOF_PRETIMEOUTE flag is not set when registering the device the
>
> WDIOF_PRETIMEOUT
>
Thanks for that finding.
> > driver will not show the sysfs entries or register the default governor.
> > By moving the registering after the decision whether pretimeout is
> > supported this gets fixed.
> >
>
> This is problematic. If the notifier is called and the watchdog is not yet
> registered, it will call watchdog_notify_pretimeout on an unregistered
> watchdog device which would crash the system. The notifier function needs
> to handle that situation. This is for both registration and removal: On
> removal, the watchdog device would be unregistered first (because of the
> use of devm_ functions) and, again, the notifier could be called on an
> unregistered watchdog device.
>
Isn't that handled in watchdog_notify_pretimeout with if (!wdd->gov)?
As I understand the code, a governor is registered earliest in
watchdog_register_pretimeout, which is called by watchdog_dev_register.
The same when doing an unregister, which should be called when doing a
watchdog_dev_unregister.
> > Signed-off-by: Stefan Eichenberger <eichest@gmail.com>
> > ---
> > drivers/watchdog/imx_sc_wdt.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/watchdog/imx_sc_wdt.c b/drivers/watchdog/imx_sc_wdt.c
> > index e9ee22a7cb45..eddb1ae630e0 100644
> > --- a/drivers/watchdog/imx_sc_wdt.c
> > +++ b/drivers/watchdog/imx_sc_wdt.c
> > @@ -183,10 +183,6 @@ static int imx_sc_wdt_probe(struct platform_device *pdev)
> > watchdog_stop_on_reboot(wdog);
> > watchdog_stop_on_unregister(wdog);
> >
> > - ret = devm_watchdog_register_device(dev, wdog);
> > - if (ret)
> > - return ret;
> > -
> > ret = imx_scu_irq_group_enable(SC_IRQ_GROUP_WDOG,
> > SC_IRQ_WDOG,
> > true);
> > @@ -213,6 +209,10 @@ static int imx_sc_wdt_probe(struct platform_device *pdev)
> > else
> > dev_warn(dev, "Add action failed, pretimeout NOT supported\n");
> >
> > + ret = devm_watchdog_register_device(dev, wdog);
> > + if (ret)
> > + return ret;
> > +
> > return 0;
>
> This is equivalent to just "return ret;".
>
Thanks, will fix that too.
Regards,
Stefan
next prev parent reply other threads:[~2021-04-05 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 12:59 [PATCH] watchdog: imx_sc_wdt: fix pretimeout eichest
2021-04-05 13:23 ` Ahmad Fatoum
2021-04-05 14:42 ` Guenter Roeck
2021-04-05 17:43 ` Stefan Eichenberger [this message]
2021-04-05 18:02 ` 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=20210405174352.GA395591@eichest-laptop \
--to=eichest@gmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wim@linux-watchdog.org \
/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;
as well as URLs for NNTP newsgroup(s).