summaryrefslogtreecommitdiffstats
path: root/net/netlabel/netlabel_user.h
diff options
context:
space:
mode:
authorHidehiro Kawai <hidehiro.kawai.ez@hitachi.com>2015-07-27 14:55:16 +0900
committerCorey Minyard <cminyard@mvista.com>2015-09-03 15:02:29 -0500
commit06e5e345fea8df24b1d935f98741343df4cab664 (patch)
tree7ba5bd37d180c796b1518199c057af065d9450c0 /net/netlabel/netlabel_user.h
parent82802f968bd3118af04eaeb3814c21d9813be527 (diff)
downloadlinux-06e5e345fea8df24b1d935f98741343df4cab664.tar.gz
linux-06e5e345fea8df24b1d935f98741343df4cab664.tar.bz2
linux-06e5e345fea8df24b1d935f98741343df4cab664.zip
ipmi: Avoid touching possible corrupted lists in the panic context
When processing queued messages in the panic context, IPMI driver tries to do it without any locking to avoid deadlocks. However, this means we can touch a corrupted list if the kernel panicked while manipulating the list. Fortunately, current `add-tail and del-from-head' style implementation won't touch the corrupted part, but it is inherently risky. To get rid of the risk, this patch re-initializes the message lists on panic if the related spinlock has already been acquired. As the result, we may lose queued messages, but it's not so painful. Dropping messages on the received message list is also less problematic because no one can respond the received messages. Signed-off-by: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com> Fixed a comment typo. Signed-off-by: Corey Minyard <cminyard@mvista.com>
Diffstat (limited to 'net/netlabel/netlabel_user.h')
0 files changed, 0 insertions, 0 deletions