From: Alejandro Cabrera <acabrera@udio.cujae.edu.cu>
To: Wim Van Sebroeck <wim@iguana.be>, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 7/10 v2] Generic Watchdog Timer Driver
Date: Wed, 22 Jun 2011 17:25:28 -0400 [thread overview]
Message-ID: <4E025DC8.9090202@udio.cujae.edu.cu> (raw)
In-Reply-To: <20110618172537.GH3441@infomag.iguana.be>
Hi
> --- linux-2.6.38-generic-part6/drivers/watchdog/core/watchdog_dev.c 2011-06-16 22:52:56.763937624 +0200
> +++ linux-2.6.38-generic-part7/drivers/watchdog/core/watchdog_dev.c 2011-06-17 09:52:32.870632731 +0200
> @@ -126,11 +126,15 @@
> * Stop the watchdog if it is still active and unmark it active.
> * This function returns zero on success or a negative errno code for
> * failure.
> + * If the 'nowayout' feature was set, the watchdog cannot be stopped.
> */
>
> static int watchdog_stop(struct watchdog_device *wddev)
> {
> - int err;
> + int err = -1;
> +
> + if (test_bit(WDOG_NO_WAY_OUT,&wdd->status))
> + return err;
>
If you return err at this point you never clean the bit WDOG_ACTIVE then
the timer will keep resetting the wdt because the bit is still active.
> if (test_bit(WDOG_ACTIVE,&wdd->status)) {
> err = wddev->ops->stop(wddev);
> @@ -151,7 +155,7 @@
> *
> * A write to a watchdog device is defined as a keepalive ping.
> * Writing the magic 'V' sequence allows the next close to turn
> - * off the watchdog.
> + * off the watchdog (if 'nowayout' is not set).
> */
>
> static ssize_t watchdog_write(struct file *file, const char __user *data,
> diff -urN linux-2.6.38-generic-part6/include/linux/watchdog.h linux-2.6.38-generic-part7/include/linux/watchdog.h
> --- linux-2.6.38-generic-part6/include/linux/watchdog.h 2011-06-17 12:17:15.285063678 +0200
> +++ linux-2.6.38-generic-part7/include/linux/watchdog.h 2011-06-17 12:17:39.205063756 +0200
> @@ -86,6 +86,7 @@
> #define WDOG_DEV_OPEN 1 /* is the watchdog opened via
> * /dev/watchdog */
> #define WDOG_EXPECT_RELEASE 2 /* did we receive the magic char ? */
> +#define WDOG_NO_WAY_OUT 3 /* is 'nowayout' feature set ? */
> };
>
> /* drivers/watchdog/core/watchdog_core.c */
> --
> 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
Participe en Universidad 2012, del 13 al 17 de febrero de 2012.
Habana, Cuba: http://www.congresouniversidad.cu
Consulte la enciclopedia colaborativa cubana. http://www.ecured.cu
Participe en el Segundo Congreso Medio Ambiente Construido y
Desarrollo Sustentable (MACDES 2011) del 6 al 9 de diciembre de 2011,
Hotel Nacional, Habana, Cuba: http://macdes.cujae.edu.cu
next prev parent reply other threads:[~2011-06-22 21:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 17:25 [PATCH 7/10 v2] Generic Watchdog Timer Driver Wim Van Sebroeck
2011-06-18 19:07 ` Arnd Bergmann
2011-06-19 10:03 ` Alan Cox
2011-06-19 11:25 ` Arnd Bergmann
2011-06-19 14:19 ` Alan Cox
2011-06-19 17:29 ` Mark Lord
2011-06-22 20:13 ` Wim Van Sebroeck
2011-06-23 14:13 ` Mark Lord
2011-06-24 14:55 ` Arnd Bergmann
2011-06-24 19:17 ` Wim Van Sebroeck
2011-06-24 21:14 ` Arnd Bergmann
2011-06-22 19:56 ` Wim Van Sebroeck
2011-06-22 21:25 ` Alejandro Cabrera [this message]
2011-06-24 19:41 ` Wim Van Sebroeck
2011-06-24 20:10 ` Alejandro Cabrera
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=4E025DC8.9090202@udio.cujae.edu.cu \
--to=acabrera@udio.cujae.edu.cu \
--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