From: Hector Palacios <hector.palacios@digi.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"wim@iguana.be" <wim@iguana.be>
Subject: Re: [PATCH v2] watchdog: core: don't try to stop device if not running
Date: Mon, 8 Apr 2013 16:14:50 +0200 [thread overview]
Message-ID: <5162D0DA.6050505@digi.com> (raw)
In-Reply-To: <20130408134118.GA18644@roeck-us.net>
On 04/08/2013 03:41 PM, Guenter Roeck wrote:
> On Mon, Apr 08, 2013 at 11:10:58AM +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>
>> ---
>>
>> Changes from v1:
>> - Make it less intrusive with 'if/else if' clauses
>> - Change the logic of 'err' variable for better readability of code
>> - Remove one-liner if brackets that broke coding sytle
>>
>> drivers/watchdog/watchdog_dev.c | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/watchdog/watchdog_dev.c b/drivers/watchdog/watchdog_dev.c
>> index ef8edec..8e0f1b8 100644
>> --- a/drivers/watchdog/watchdog_dev.c
>> +++ b/drivers/watchdog/watchdog_dev.c
>> @@ -463,15 +463,17 @@ out:
>> static int watchdog_release(struct inode *inode, struct file *file)
>> {
>> struct watchdog_device *wdd = file->private_data;
>> - int err = -EBUSY;
>> + int err = 0;
>>
>> /*
>> * 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))
>> + if (test_bit(WDOG_ACTIVE, &wdd->status))
>> + err = -EBUSY;
>> + else if (test_and_clear_bit(WDOG_ALLOW_RELEASE, &wdd->status) ||
>> + !(wdd->info->options & WDIOF_MAGICCLOSE))
>> err = watchdog_stop(wdd);
>>
> Looking at it again, it is now broken and fails with EBUSY if WDOG_ACTIVE is
> set, and it tries to stop the watchdog if it is already stopped.
You are right, good catch! So your patch version wins.
Thank you
--
Héctor Palacios
--
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:[~2013-04-08 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 9:10 [PATCH v2] watchdog: core: don't try to stop device if not running Hector Palacios
2013-04-08 13:41 ` Guenter Roeck
2013-04-08 14:14 ` Hector Palacios [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=5162D0DA.6050505@digi.com \
--to=hector.palacios@digi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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