From: Wim Van Sebroeck <wim@iguana.be>
To: Hector Palacios <hector.palacios@digi.com>
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@roeck-us.net
Subject: Re: [PATCH v3] watchdog: core: don't try to stop device if not running
Date: Sun, 26 May 2013 18:51:39 +0200 [thread overview]
Message-ID: <20130526165139.GA8365@spo001.leaseweb.com> (raw)
In-Reply-To: <1365433592-25687-1-git-send-email-hector.palacios@digi.com>
Hi Hector,
> 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.
> Changes from v2:
> - Revert "Change the logic of 'err'..." from v1 because otherwise the
> 'else if' can't be reached if the watchdog is running.
>
> drivers/watchdog/watchdog_dev.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
Patch added to linux-watchdog-next.
Kind regards,
Wim.
prev parent reply other threads:[~2013-05-26 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 15:06 Hector Palacios
2013-04-08 15:16 ` Guenter Roeck
2013-05-26 16:51 ` Wim Van Sebroeck [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=20130526165139.GA8365@spo001.leaseweb.com \
--to=wim@iguana.be \
--cc=hector.palacios@digi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
/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
all inboxes | Powered by JetHome®