summaryrefslogtreecommitdiffstats
path: root/drivers/char/rtc.c
diff options
context:
space:
mode:
authorHidehiro Kawai <hidehiro.kawai.ez@hitachi.com>2015-04-23 11:16:44 +0900
committerCorey Minyard <cminyard@mvista.com>2015-05-05 19:33:49 -0500
commit9f8127048ab8b47b43f8aeaaec9fec2da44be9a1 (patch)
treeded69906802d1151af32d5e1f150f87306d6127b /drivers/char/rtc.c
parenta182a4b2b3e85a559ea2cd3545f4311db41325f2 (diff)
downloadlinux-stable-9f8127048ab8b47b43f8aeaaec9fec2da44be9a1.tar.gz
linux-stable-9f8127048ab8b47b43f8aeaaec9fec2da44be9a1.tar.bz2
linux-stable-9f8127048ab8b47b43f8aeaaec9fec2da44be9a1.zip
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>
Diffstat (limited to 'drivers/char/rtc.c')
0 files changed, 0 insertions, 0 deletions