From: Corey Minyard <minyard@acm.org>
To: Mark Rustad <MRustad@gmail.com>
Cc: openipmi-developer@lists.sourceforge.net, wim@iguana.be,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [Openipmi-developer] [PATCH] IPMI: return correct value from ipmi_write
Date: Thu, 10 Jul 2008 15:16:46 -0500 [thread overview]
Message-ID: <48766E2E.4060701@acm.org> (raw)
In-Reply-To: <4876628f.41O/uzQ5H7nSU2Vg%MRustad@gmail.com>
This patch is correct.
Signed-off-by: Corey Minyard <cminyard@mvista.com>
Mark Rustad wrote:
> From: Mark Rustad <MRustad@gmail.com>
>
> This patch corrects the handling of write operations to the IPMI watchdog
> to work as intended by returning the number of characters actually
> processed. Without this patch, an "echo V >/dev/watchdog" enables the
> watchdog if IPMI is providing the watchdog function.
>
> Signed-off-by: Mark Rustad <MRustad@gmail.com>
> ---
> I have not checked all of the watchdogs to see if there are others that have
> this problem, but the one I was using before using the IPMI one did work
> right. It was also a big surprise how much the default watchdog timeout
> varies from one to another. Let me tell you that the 10 second default
> for the IPMI watchdog was a real sore spot while tracking this problem down!
> This problem goes back at least as far as 2.6.20, but I generated this patch
> based on 2.6.26-rc9. I have applied, compiled and tested this fix.
>
> drivers/char/ipmi/ipmi_watchdog.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> --- a/drivers/char/ipmi/ipmi_watchdog.c 2008-07-10 09:31:52.000000000 -0500
> +++ b/drivers/char/ipmi/ipmi_watchdog.c 2008-07-10 09:33:41.000000000 -0500
> @@ -755,9 +755,8 @@ static ssize_t ipmi_write(struct file *f
> rv = ipmi_heartbeat();
> if (rv)
> return rv;
> - return 1;
> }
> - return 0;
> + return len;
> }
>
> static ssize_t ipmi_read(struct file *file,
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Openipmi-developer mailing list
> Openipmi-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openipmi-developer
>
next prev parent reply other threads:[~2008-07-10 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 19:27 [PATCH] IPMI: return correct value from ipmi_write Mark Rustad
2008-07-10 20:16 ` Corey Minyard [this message]
2008-07-11 11:58 ` [Openipmi-developer] " Wim Van Sebroeck
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=48766E2E.4060701@acm.org \
--to=minyard@acm.org \
--cc=MRustad@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.