| commit | 152e9145400e422015d7715446a85b0b4bfae38e | [log] [tgz] |
|---|---|---|
| author | Johnathan Mantey <johnathanx.mantey@intel.com> | Thu Jun 15 13:46:02 2023 -0700 |
| committer | Vernon Mauery <vernon.mauery@linux.intel.com> | Fri Jun 16 21:51:50 2023 +0000 |
| tree | 1a5a5d32a89c07eb17ae719c63706820ec5ec8ac | |
| parent | ae339045b4fe94477e1823ac18c5f23016a54b2d [diff] |
Fix IPMI firmware update programming failure The IPMI Firmware Update sequence fails on some systems. The update process receives the new firmware image data in the /tmp file system. During the final update phase the image is copied into the /tmp/images subdirectory. If /tmp and /tmp/images are not part of the same filesystem the std::filesystem::rename() function fails. This commit changes the update process. The rename() is still attempted. In the event the rename() fails, a copy() operation is performed in the belief the destination is on a separate filesystem. Tested: Confirmed this change works on systems with a common /tmp filesystem. Confirmed this change works on systems with the source file and the destination file on different filesystems. Change-Id: I5e3da6c0f453941ea54cb829d2bcaeadda0db438 Signed-off-by: Johnathan Mantey <johnathanx.mantey@intel.com>
This component is intended to provide Intel-specific IPMI[3] command handlers for OpenBMC. These handlers are intended to integrate BMC with servers based on Intel architecture.
intel-ipmi-oem serves as an extension[1] to OpenBMC IPMI daemon[2]. It is compiled as a shared library and intended to both:
Related features provided by the library are grouped in separate source files. Main extensions to vanilla OpenBMC IPMI stack are the following:
[4]