From: Corey Minyard <minyard@acm.org>
To: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Cc: openipmi-developer@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipmi: Fix a problem that messages are not issued in run_to_completion mode
Date: Wed, 06 May 2015 07:27:59 -0500 [thread overview]
Message-ID: <554A08CF.4000509@acm.org> (raw)
In-Reply-To: <553F8004.8020408@hitachi.com>
On 04/28/2015 07:41 AM, Hidehiro Kawai wrote:
> Hello,
>
> (2015/04/24 22:00), Corey Minyard wrote:
>> Ah, yes, you are correct. Queued for 4.1. Thanks.
> Thank you for the review.
>
> By the way, I'm planning some enhancements of IPMI driver
> in panic context. Currently, we can call panic notifiers
> before crash_kexec() by specifying crash_kexec_post_notifiers
> as a boot parameter. By utilizing this feature, we can write
> SEL records before entering kdump process; we can save some
> information even if kdump fails. Here, notifier calls
> shouldn't prevent the kdump process. So, the reliability of
> panic notifier calls is very important.
I thought these were called before crash_kexec(). But if not that would
be a good enhancement.
> I noticed that there are possible infinite loops in the
> panic notifier call of IPMI driver (we assume BMC is
> unreliable). To evict possible infinite loops, I'm considering
> introducing some retry timeout or retry count limit to the
> run_to_completion procedure.
>
> Do you have any opinions?
That's probably a good idea. My thought was to keep trying in hopes of
getting something out, but you are probably right, a timeout after a few
minutes is probably appropriate.
-corey
next prev parent reply other threads:[~2015-05-06 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 2:16 [PATCH] ipmi: Fix a problem that messages are not issued in run_to_completion mode Hidehiro Kawai
2015-04-24 13:00 ` Corey Minyard
2015-04-28 12:41 ` Hidehiro Kawai
2015-05-06 12:27 ` Corey Minyard [this message]
2015-05-07 12:01 ` Hidehiro Kawai
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=554A08CF.4000509@acm.org \
--to=minyard@acm.org \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.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