Google GitGoogle Git
Sign in
gbmc/pldm/f6d6e01716d13bae1ce460ee00b7966734a9f523
commit
f6d6e01716d13bae1ce460ee00b7966734a9f523
[log]
author
JY Voon <jvoon@nvidia.com>
Tue Jul 07 14:34:31 2026 +0900
committer
ManojKiran Eda <manojkiran.eda@gmail.com>
Fri Jul 17 05:22:44 2026 +0000
tree
31409f01b0883e0cca17b252844c3d690b86f308
parent
db7aa157bee691a97de41d409c3d29484bb80e11 [diff]
libpldmresponder: guard null host-path handlers

pldmd only constructs hostPDRHandler and dbusToPLDMEventHandler when a
host EID is configured, but three paths dereference them
unconditionally, crashing pldmd on hostless platforms:

- pldmPDRRepositoryChgEvent() marks and consumes hostPDRHandler for
  every PDR repository change event; guard those uses.
- getStateSensorReadings() reads the sensor cache from
  dbusToPLDMEventHandler; fall back to an empty cache, so previousState
  reports PLDM_SENSOR_UNKNOWN as on a first read.
- The OemIBM constructor wires the OEM handlers into hostPDRHandler;
  skip the wiring when the handler does not exist.

Add regression tests for the two responder paths. The new event test
surfaced a misaligned uint32_t read of the changeEntry array in
getPDRRecordHandles(); copy each entry with memcpy instead.

Change-Id: I5118ff9786254799790c848a68bdde5e6f6f2dfc
Signed-off-by: JY Voon <jvoon@nvidia.com>
3 files changed
tree: 31409f01b0883e0cca17b252844c3d690b86f308
  1. common/
  2. configurations/
  3. docs/
  4. fw-update/
  5. host-bmc/
  6. libpldmresponder/
  7. oem/
  8. platform-mc/
  9. pldmd/
  10. pldmtool/
  11. requester/
  12. softoff/
  13. subprojects/
  14. test/
  15. tools/
  16. utilities/
  17. .clang-format
  18. .clang-tidy
  19. .eslintignore
  20. .gitignore
  21. .linter-ignore
  22. LICENSE
  23. meson.build
  24. meson.options
  25. OWNERS
  26. README.md
README.md

PLDM - Platform Level Data Model

License

Overview

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.

Features

  • Standardized Messaging: Adheres to the DMTF's PLDM specifications, enabling consistent and interoperable communication between different components.
  • Modularity: Supports multiple PLDM types, including base, FRU,Firmware update, Platform Monitoring and Control, and BIOS Control and Configuration.
  • Extensibility: Easily extendable to support new PLDM types and custom OEM commands.
  • Integration: Seamlessly integrates with other OpenBMC components for comprehensive system management.

Getting Started

Prerequisites

To build and run PLDM, you need the following dependencies:

  • Meson
  • Ninja

Alternatively, source an OpenBMC ARM/x86 SDK.

Building

To build the PLDM project, follow these steps:

meson setup build && meson compile -C build

To run unit tests

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.

To enable pldm verbosity

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

To disable pldm verbosity

rm /etc/default/pldmd
systemctl restart pldmd

Documentation

For complete documentation on the functionality and usage of this repository, please refer to the docs folder.