From: Guenter Roeck <linux@roeck-us.net>
To: Tao Ren <taoren@fb.com>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH] watchdog: core: suppress "watchdog did not stop" message
Date: Thu, 15 Nov 2018 16:19:38 -0800 [thread overview]
Message-ID: <20181116001938.GA16009@roeck-us.net> (raw)
In-Reply-To: <20181115234413.27009-1-taoren@fb.com>
On Thu, Nov 15, 2018 at 11:44:26PM +0000, Tao Ren wrote:
> Currently "watchdog did not stop!" message is printed when the watchdog
> timer is not stopped at close. For example, people may see the message
> when rebooting the system, or the message will be logged to console
> periodically if watchdog is kicked by a scirpt which runs "echo k >
> /dev/watchdog" command.
>
> Given a critical message usually indicates a serious hardware/software
> failure, this message could easily lead to confusion, so it's better to
> just delete the message.
>
> Signed-off-by: Tao Ren <taoren@fb.com>
NACK. This message is displayed if/when the watchdog application
exits without stopping the watchdog and/or without closing properly.
This _is_ critical since it will reboot the system after the next
timeout period.
If userspace triggers this message on purpose (eg by the mentioned
script, which does not exit properly), userspace is at fault,
not the kernel.
Guenter
> ---
> drivers/watchdog/watchdog_dev.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/watchdog/watchdog_dev.c b/drivers/watchdog/watchdog_dev.c
> index f6c24b22b37c..65e9ebbd8759 100644
> --- a/drivers/watchdog/watchdog_dev.c
> +++ b/drivers/watchdog/watchdog_dev.c
> @@ -879,7 +879,6 @@ static int watchdog_release(struct inode *inode, struct file *file)
>
> /* If the watchdog was not stopped, send a keepalive ping */
> if (err < 0) {
> - pr_crit("watchdog%d: watchdog did not stop!\n", wdd->id);
> watchdog_ping(wdd);
> }
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2018-11-16 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 23:44 [PATCH] watchdog: core: suppress "watchdog did not stop" message Tao Ren
2018-11-16 0:19 ` Guenter Roeck [this message]
2018-11-16 0:37 ` Tao Ren
2018-11-27 1:31 ` Jerry Hoemann
2018-11-27 6:11 ` Tao Ren
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=20181116001938.GA16009@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=taoren@fb.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.