From: Corey Minyard <minyard@acm.org>
To: Robert Lippert <roblip@gmail.com>
Cc: Robert Lippert <rlippert@google.com>,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipmi/watchdog: fix wdog hang on panic waiting for ipmi response
Date: Fri, 28 Apr 2017 14:53:06 -0500 [thread overview]
Message-ID: <9175e5aa-4fd7-4e25-8edd-a4b7460fcebb@acm.org> (raw)
In-Reply-To: <20170420234947.1037-1-rlippert@google.com>
On 04/20/2017 06:49 PM, Robert Lippert wrote:
> Commit c49c097610fe ("ipmi: Don't call receive handler in the
> panic context") means that the panic_recv_free is not called during a
> panic and the atomic count does not drop to 0.
>
> Fix this by only expecting one decrement of the atomic variable
> which comes from panic_smi_free.
Thanks, queued for the next kernel release.
-corey
> Signed-off-by: Robert Lippert <rlippert@google.com>
> ---
>
> drivers/char/ipmi/ipmi_watchdog.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/char/ipmi/ipmi_watchdog.c b/drivers/char/ipmi/ipmi_watchdog.c
> index 5ca24d9b101b..d165af8abe36 100644
> --- a/drivers/char/ipmi/ipmi_watchdog.c
> +++ b/drivers/char/ipmi/ipmi_watchdog.c
> @@ -516,7 +516,7 @@ static void panic_halt_ipmi_heartbeat(void)
> msg.cmd = IPMI_WDOG_RESET_TIMER;
> msg.data = NULL;
> msg.data_len = 0;
> - atomic_add(2, &panic_done_count);
> + atomic_add(1, &panic_done_count);
> rv = ipmi_request_supply_msgs(watchdog_user,
> (struct ipmi_addr *) &addr,
> 0,
> @@ -526,7 +526,7 @@ static void panic_halt_ipmi_heartbeat(void)
> &panic_halt_heartbeat_recv_msg,
> 1);
> if (rv)
> - atomic_sub(2, &panic_done_count);
> + atomic_sub(1, &panic_done_count);
> }
>
> static struct ipmi_smi_msg panic_halt_smi_msg = {
> @@ -550,12 +550,12 @@ static void panic_halt_ipmi_set_timeout(void)
> /* Wait for the messages to be free. */
> while (atomic_read(&panic_done_count) != 0)
> ipmi_poll_interface(watchdog_user);
> - atomic_add(2, &panic_done_count);
> + atomic_add(1, &panic_done_count);
> rv = i_ipmi_set_timeout(&panic_halt_smi_msg,
> &panic_halt_recv_msg,
> &send_heartbeat_now);
> if (rv) {
> - atomic_sub(2, &panic_done_count);
> + atomic_sub(1, &panic_done_count);
> printk(KERN_WARNING PFX
> "Unable to extend the watchdog timeout.");
> } else {
prev parent reply other threads:[~2017-04-28 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 23:49 Robert Lippert
2017-04-28 19:53 ` Corey Minyard [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=9175e5aa-4fd7-4e25-8edd-a4b7460fcebb@acm.org \
--to=minyard@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=rlippert@google.com \
--cc=roblip@gmail.com \
/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®