summaryrefslogtreecommitdiffstats
path: root/drivers/base
diff options
context:
space:
mode:
authorPaolo Galtieri <pgaltieri@mvista.com>2005-12-15 12:34:28 -0800
committerLinus Torvalds <torvalds@g5.osdl.org>2005-12-15 14:22:45 -0800
commit7767e126ca0f32cd0438455fdd9650f909d2eeb3 (patch)
treeefcad511a28e5b78db8d666c78636c55b664a1a0 /drivers/base
parentebbd1bce79b3b4778d9e1914a22c42fcfa869cd9 (diff)
downloadop-kernel-dev-7767e126ca0f32cd0438455fdd9650f909d2eeb3.zip
op-kernel-dev-7767e126ca0f32cd0438455fdd9650f909d2eeb3.tar.gz
[PATCH] IPMI oops fix
While doing some testing I discovered that if the BIOS on a board does not properly setup the DMI information it leads to a panic in the IPMI code. The panic is due to dereferencing a pointer which is not initialized. The pointer is initialized in port_setup() and/or mem_setup() and used in init_one_smi() and cleanup_one_si(), however if either port_setup() or mem_setup() return ENODEV the pointer does not get initialized. Signed-off-by: Paolo Galtieri <pgaltieri@mvista.com> Acked-by: Corey Minyard <cminyard@mvista.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'drivers/base')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud