LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Jan Kiszka <jan.kiszka@web.de>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] watchdog: Start watchdog in watchdog_set_last_hw_keepalive only if appropriate
Date: Sun, 1 Aug 2021 10:37:53 -0700 [thread overview]
Message-ID: <7228af51-5390-23e8-1383-b196e44a669a@roeck-us.net> (raw)
In-Reply-To: <93d56386-6e37-060b-55ce-84de8cde535f@web.de>
On 8/1/21 12:56 AM, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> We must not pet a running watchdog when handle_boot_enabled is off
> because this will kick off automatic triggering before userland is
> running, defeating the purpose of the handle_boot_enabled control.
> Furthermore, don't ping in case watchdog_set_last_hw_keepalive was
> called incorrectly when the hardware watchdog is actually not running.
>
> Fixed: cef9572e9af3 ("watchdog: add support for adjusting last known HW keepalive time")
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> ---
>
> Changes to v1 ("watchdog: Respect handle_boot_enabled when setting last last_hw_keepalive"):
> - add watchdog_hw_running test
> - improve commit log
>
> drivers/watchdog/watchdog_dev.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/watchdog/watchdog_dev.c b/drivers/watchdog/watchdog_dev.c
> index 3bab32485273..6c73160386b9 100644
> --- a/drivers/watchdog/watchdog_dev.c
> +++ b/drivers/watchdog/watchdog_dev.c
> @@ -1172,7 +1172,10 @@ int watchdog_set_last_hw_keepalive(struct watchdog_device *wdd,
>
> wd_data->last_hw_keepalive = ktime_sub(now, ms_to_ktime(last_ping_ms));
>
> - return __watchdog_ping(wdd);
> + if (watchdog_hw_running(wdd) && handle_boot_enabled)
> + return __watchdog_ping(wdd);
> +
> + return 0;
> }
> EXPORT_SYMBOL_GPL(watchdog_set_last_hw_keepalive);
>
> --
> 2.31.1
>
prev parent reply other threads:[~2021-08-01 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 7:56 Jan Kiszka
2021-08-01 17:37 ` Guenter Roeck [this message]
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=7228af51-5390-23e8-1383-b196e44a669a@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jan.kiszka@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@linux-watchdog.org \
--subject='Re: [PATCH v2] watchdog: Start watchdog in watchdog_set_last_hw_keepalive only if appropriate' \
/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
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).