public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Hector Palacios <hector.palacios@digi.com>
Cc: linux-watchdog@vger.kernel.org, wim@iguana.be,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] watchdog: core: don't try to stop device if not running
Date: Fri, 5 Apr 2013 11:34:50 -0700	[thread overview]
Message-ID: <20130405183450.GA29835@roeck-us.net> (raw)
In-Reply-To: <515EF748.6060504@digi.com>

On Fri, Apr 05, 2013 at 06:09:44PM +0200, Hector Palacios wrote:
> A watchdog device may be stopped from userspace using WDIOC_SETOPTIONS
> ioctl and flag WDIOS_DISABLECARD. If the device is closed after this
> operation, watchdog_release() is called and status bits checked for
> stopping it. Besides, if the device has not been unregistered a critical
> message "watchdog did not stop!" is printed, although the ioctl may have
> successfully stopped it already.
> 
> Without the patch a user application sample code like this will successfully
> stop the watchdog, but the kernel will output the message
> "watchdog did not stop!":
> 
> 	wd_fd = open("/dev/watchdog", O_RDWR);
> 
> 	flags = WDIOS_DISABLECARD;
> 	ioctl(wd_fd, WDIOC_SETOPTIONS, &flags);
> 
> 	close(wd_fd);
> 
> Signed-off-by: Hector Palacios <hector.palacios@digi.com>

How about the following patch instead ?

diff --git a/drivers/watchdog/watchdog_dev.c b/drivers/watchdog/watchdog_dev.c
index 08b48bb..9775e8d 100644
--- a/drivers/watchdog/watchdog_dev.c
+++ b/drivers/watchdog/watchdog_dev.c
@@ -469,7 +469,9 @@ static int watchdog_release(struct inode *inode, struct file *file)
 	 * or if WDIOF_MAGICCLOSE is not set. If nowayout was set then
 	 * watchdog_stop will fail.
 	 */
-	if (test_and_clear_bit(WDOG_ALLOW_RELEASE, &wdd->status) ||
+	if (!test_bit(WDOG_ACTIVE, &wdd->status))
+		err = 0;
+	else if (test_and_clear_bit(WDOG_ALLOW_RELEASE, &wdd->status) ||
 	    !(wdd->info->options & WDIOF_MAGICCLOSE))
 		err = watchdog_stop(wdd);

Much less invasive and the result is the same.

Thanks,
Guenter

> ---
>  drivers/watchdog/watchdog_dev.c |   38 +++++++++++++++++++++-----------------
>  1 file changed, 21 insertions(+), 17 deletions(-)
> 
> diff --git a/drivers/watchdog/watchdog_dev.c b/drivers/watchdog/watchdog_dev.c
> index ef8edec..adadbdd 100644
> --- a/drivers/watchdog/watchdog_dev.c
> +++ b/drivers/watchdog/watchdog_dev.c
> @@ -463,24 +463,28 @@ out:
>  static int watchdog_release(struct inode *inode, struct file *file)
>  {
>  	struct watchdog_device *wdd = file->private_data;
> -	int err = -EBUSY;
> 
> -	/*
> -	 * We only stop the watchdog if we received the magic character
> -	 * or if WDIOF_MAGICCLOSE is not set. If nowayout was set then
> -	 * watchdog_stop will fail.
> -	 */
> -	if (test_and_clear_bit(WDOG_ALLOW_RELEASE, &wdd->status) ||
> -	    !(wdd->info->options & WDIOF_MAGICCLOSE))
> -		err = watchdog_stop(wdd);
> -
> -	/* If the watchdog was not stopped, send a keepalive ping */
> -	if (err < 0) {
> -		mutex_lock(&wdd->lock);
> -		if (!test_bit(WDOG_UNREGISTERED, &wdd->status))
> -			dev_crit(wdd->dev, "watchdog did not stop!\n");
> -		mutex_unlock(&wdd->lock);
> -		watchdog_ping(wdd);
> +	if (test_bit(WDOG_ACTIVE, &wdd->status)) {
> +		int err = -EBUSY;
> +
> +		/*
> +		 * We only stop the watchdog if we received the magic character
> +		 * or if WDIOF_MAGICCLOSE is not set. If nowayout was set then
> +		 * watchdog_stop will fail.
> +		 */
> +		if (test_and_clear_bit(WDOG_ALLOW_RELEASE, &wdd->status) ||
> +		    !(wdd->info->options & WDIOF_MAGICCLOSE)) {
> +			err = watchdog_stop(wdd);
> +		}
> +
> +		/* If the watchdog was not stopped, send a keepalive ping */
> +		if (err < 0) {
> +			mutex_lock(&wdd->lock);
> +			if (!test_bit(WDOG_UNREGISTERED, &wdd->status))
> +				dev_crit(wdd->dev, "watchdog did not stop!\n");
> +			mutex_unlock(&wdd->lock);
> +			watchdog_ping(wdd);
> +		}
>  	}
> 
>  	/* Allow the owner module to be unloaded again */
> -- 
> 1.7.9.5
> --
> 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
> 

  reply	other threads:[~2013-04-05 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 16:09 [PATCH RFC] watchdog: core: don't try to stop device if not running Hector Palacios
2013-04-05 18:34 ` Guenter Roeck [this message]
2013-04-08  7:48   ` Hector Palacios
2013-04-08  8:16     ` Guenter Roeck
2013-04-08  8:43       ` Hector Palacios

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=20130405183450.GA29835@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=hector.palacios@digi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --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