From: Guenter Roeck <linux@roeck-us.net>
To: Tomas Winkler <tomas.winkler@intel.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org,
Alexander Usyskin <alexander.usyskin@intel.com>
Subject: Re: [watchdog-next] watchdog: core: propagate ping error code to the user space
Date: Mon, 26 Oct 2015 05:32:22 -0700 [thread overview]
Message-ID: <20151026123113.GA23571@roeck-us.net> (raw)
In-Reply-To: <1445861278-18213-1-git-send-email-tomas.winkler@intel.com>
On Mon, Oct 26, 2015 at 02:07:58PM +0200, Tomas Winkler wrote:
> From: Alexander Usyskin <alexander.usyskin@intel.com>
>
> Watchdog ping return errors are ignored by watchdog core,
> Whatchdog daemon should be informed about possible hardware error or
> underlaying device driver get unregistered.
>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
Makes sense to me, so
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
I do wonder, though, if there was a reason for ignoring the result
from the ping operation, or if that is purely historic.
Guenter
> ---
> drivers/watchdog/watchdog_dev.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/watchdog/watchdog_dev.c b/drivers/watchdog/watchdog_dev.c
> index 6aaefbad303e..423a7e0dd919 100644
> --- a/drivers/watchdog/watchdog_dev.c
> +++ b/drivers/watchdog/watchdog_dev.c
> @@ -295,6 +295,7 @@ static ssize_t watchdog_write(struct file *file, const char __user *data,
> struct watchdog_device *wdd = file->private_data;
> size_t i;
> char c;
> + int err;
>
> if (len == 0)
> return 0;
> @@ -314,7 +315,9 @@ static ssize_t watchdog_write(struct file *file, const char __user *data,
> }
>
> /* someone wrote to us, so we send the watchdog a keepalive ping */
> - watchdog_ping(wdd);
> + err = watchdog_ping(wdd);
> + if (err < 0)
> + return err;
>
> return len;
> }
> @@ -370,8 +373,7 @@ static long watchdog_ioctl(struct file *file, unsigned int cmd,
> case WDIOC_KEEPALIVE:
> if (!(wdd->info->options & WDIOF_KEEPALIVEPING))
> return -EOPNOTSUPP;
> - watchdog_ping(wdd);
> - return 0;
> + return watchdog_ping(wdd);
> case WDIOC_SETTIMEOUT:
> if (get_user(val, p))
> return -EFAULT;
> @@ -381,7 +383,9 @@ static long watchdog_ioctl(struct file *file, unsigned int cmd,
> /* If the watchdog is active then we send a keepalive ping
> * to make sure that the watchdog keep's running (and if
> * possible that it takes the new timeout) */
> - watchdog_ping(wdd);
> + err = watchdog_ping(wdd);
> + if (err < 0)
> + return err;
> /* Fall */
> case WDIOC_GETTIMEOUT:
> /* timeout == 0 means that we don't know the timeout */
> --
> 2.4.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-10-26 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 12:07 [watchdog-next] watchdog: core: propagate ping error code to the user space Tomas Winkler
2015-10-26 12:32 ` 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=20151026123113.GA23571@roeck-us.net \
--to=linux@roeck-us.net \
--cc=alexander.usyskin@intel.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--cc=wim@iguana.be \
/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