From: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
To: minyard@acm.org
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: Tue, 28 Apr 2015 21:41:40 +0900 [thread overview]
Message-ID: <553F8004.8020408@hitachi.com> (raw)
In-Reply-To: <553A3E7D.6040207@acm.org>
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 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?
--
Hidehiro Kawai
Hitachi, Ltd. Research & Development Group
next prev parent reply other threads:[~2015-04-28 12:41 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 [this message]
2015-05-06 12:27 ` Corey Minyard
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=553F8004.8020408@hitachi.com \
--to=hidehiro.kawai.ez@hitachi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.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