platform-mc: Fix null deref in initTerminus Commit [1] changed initTerminus() to snapshot TIDs before iterating, but the loop still looks up each terminus by TID using operator[]. If a terminus is removed between iterations, operator[] silently inserts a null entry instead of failing, causing a null pointer dereference on the next access. Add a contains() guard before the lookup so that removed TIDs are skipped, consistent with the existing guards after each co_await. Tested: On a Yosemite 4 platform, repeated chassis power cycles trigger the race. With the fix applied and a temporary log confirming the guard fires, initTerminus completes without crash. Reference: [1] https://gerrit.openbmc.org/c/openbmc/pldm/+/89709 Change-Id: I948d78bfd6087ac2496489752a3291ce5f34eb68 Signed-off-by: Eric Yang <eric.yang.wiwynn@gmail.com>
PLDM (Platform Level Data Model) is a key component of the OpenBMC project, providing a standardized data model and message formats for various platform management functionalities. It defines a method to manage, monitor, and control the firmware and hardware of a system.
The OpenBMC PLDM project aims to implement the specifications defined by the Distributed Management Task Force (DMTF), allowing for interoperable management interfaces across different hardware and firmware components.
To build and run PLDM, you need the following dependencies:
MesonNinjaAlternatively, source an OpenBMC ARM/x86 SDK.
To build the PLDM project, follow these steps:
meson setup build && meson compile -C build
The simplest way of running the tests is as described by the meson man page:
meson test -C build
Alternatively, tests can be run in the OpenBMC CI docker container using these steps.
pldm daemon accepts a command line argument --verbose or --v or -v to enable the daemon to run in verbose mode. It can be done via adding this option to the environment file that pldm service consumes.
echo 'PLDMD_ARGS="--verbose"' > /etc/default/pldmd systemctl restart pldmd
rm /etc/default/pldmd systemctl restart pldmd
For complete documentation on the functionality and usage of this repository, please refer to the docs folder.