| /openbmc/ipmitool/src/plugins/lanplus/ |
| H A D | lanplus_crypt.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| H A D | lanplus.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| /openbmc/ipmitool/src/ |
| H A D | ipmishell.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| H A D | ipmievd.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| /openbmc/ipmitool/include/ipmitool/ |
| H A D | ipmi_intf.h | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| /openbmc/ipmitool/lib/ |
| H A D | ipmi_tsol.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| H A D | ipmi_sol.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| H A D | ipmi_dcmi.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| H A D | ipmi_hpmfwupg.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| H A D | ipmi_main.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| /openbmc/ipmitool/src/plugins/serial/ |
| H A D | serial_terminal.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| H A D | serial_basic.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| /openbmc/ipmitool/src/plugins/lan/ |
| H A D | lan.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|
| /openbmc/ipmitool/src/plugins/ |
| H A D | ipmi_intf.c | diff eb54136775f63a6a159f3c55ee4772d7aa363cc4 Wed Mar 11 13:41:34 CDT 2015 Zdenek Styblik <stybla@turnovfree.net> ID:319 - Interface safe re-open
Currently, interface-management code in the ipmitool does not allow safe
interface re-opening (i.e. closing and opening again). It is because the session
is allocated in the interface setup callback while is freed in the close
callback. So, normal re-opening of the interface, which can be required for
example durng the HPM.1 upgrade, leads to segmentation fault. That's why in the
ipmi_hpmfwupg.c instead of normal closing interface, directly access the
interface data for subsequent re-opening.
Commit for Dmitry Bazhenov
|