ipmi: Fix a problem that messages are not issued in run_to_completion mode
authorHidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Thu, 23 Apr 2015 02:16:44 +0000 (11:16 +0900)
committerCorey Minyard <cminyard@mvista.com>
Wed, 6 May 2015 00:33:49 +0000 (19:33 -0500)
commit9f8127048ab8b47b43f8aeaaec9fec2da44be9a1
treeded69906802d1151af32d5e1f150f87306d6127b
parenta182a4b2b3e85a559ea2cd3545f4311db41325f2
ipmi: Fix a problem that messages are not issued in run_to_completion mode

start_next_msg() issues a message placed in smi_info->waiting_msg
if it is non-NULL.  However, sender() sets a message to
smi_info->curr_msg and NULL to smi_info->waiting_msg in the context
of run_to_completion mode.  As the result, it leads an infinite
loop by waiting the completion of unissued message when leaving
dying message after kernel panic.

sender() should set the message to smi_info->waiting_msg not
curr_msg.

Signed-off-by: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Signed-off-by: Corey Minyard <cminyard@mvista.com>
drivers/char/ipmi/ipmi_si_intf.c