aboutsummaryrefslogtreecommitdiffstats
path: root/include/net/sock.h
diff options
context:
space:
mode:
authorTony Camuso <tcamuso@redhat.com>2019-04-09 15:20:03 -0400
committerCorey Minyard <cminyard@mvista.com>2019-04-16 21:36:49 +0000
commita885bcfd152f97b25005298ab2d6b741aed9b49c (patch)
tree640e87088c272104b0acb33a47f8da0fa1227bca /include/net/sock.h
parentipmi: Fix failure on SMBIOS specified devices (diff)
downloadlinux-dev-a885bcfd152f97b25005298ab2d6b741aed9b49c.tar.xz
linux-dev-a885bcfd152f97b25005298ab2d6b741aed9b49c.zip
ipmi: ipmi_si_hardcode.c: init si_type array to fix a crash
The intended behavior of function ipmi_hardcode_init_one() is to default to kcs interface when no type argument is presented when initializing ipmi with hard coded addresses. However, the array of char pointers allocated on the stack by function ipmi_hardcode_init() was not inited to zeroes, so it contained stack debris. Consequently, passing the cruft stored in this array to function ipmi_hardcode_init_one() caused a crash when it was unable to detect that the char * being passed was nonsense and tried to access the address specified by the bogus pointer. The fix is simply to initialize the si_type array to zeroes, so if there were no type argument given to at the command line, function ipmi_hardcode_init_one() could properly default to the kcs interface. Signed-off-by: Tony Camuso <tcamuso@redhat.com> Message-Id: <1554837603-40299-1-git-send-email-tcamuso@redhat.com> Signed-off-by: Corey Minyard <cminyard@mvista.com>
Diffstat (limited to 'include/net/sock.h')
0 files changed, 0 insertions, 0 deletions