Google GitGoogle Git
Sign in
gbmc/pldm/9969353fd647ca8c4d2fc43a306ce387cc394830
commit
9969353fd647ca8c4d2fc43a306ce387cc394830
[log]
author
Guangzong Chen <guangzong@google.com>
Tue Aug 25 18:52:48 2026 +0000
committer
Guangzong Chen <guangzong@google.com>
Thu Aug 27 16:28:48 2026 +0000
tree
b13191a7a4a0a2e8e72fc4b99d2594649ece8883
parent
e0ea17efc683421a60aacbf1292a4244913dcf85 [diff]
pldmd: do not exit on recv fail with af-mctp transport

Under the Linux kernel AF_MCTP transport, transient receive failures
(e.g., PLDM_REQUESTER_RECV_FAIL returned when a downstream endpoint is
resetting, disconnected, or sending unmapped packets) do not indicate
that the underlying transport socket has been closed by a daemon.

Exiting the event loop on PLDM_REQUESTER_RECV_FAIL was originally
introduced for mctp-demux UNIX domain sockets, where recv failure
indicated the demux daemon process had terminated. In the AF_MCTP
architecture, this causes pldmd to terminate and restart unnecessarily
whenever a downstream device resets.

Restrict the socket-close exit logic to PLDM_TRANSPORT_WITH_MCTP_DEMUX
so that AF_MCTP logs a warning and continues event processing.

Tested: Verified error handling for AF_MCTP transport.
Google-Bug-Id: 543041824
Change-Id: I5c1b0c0b57dd6e27d173bdceaf0cd80010b0afee
Signed-off-by: Guangzong Chen <guangzong@google.com>
TAG=agy
CONV=f6e4e885-dc2d-47ba-99c7-be407d766de9
1 file changed
tree: b13191a7a4a0a2e8e72fc4b99d2594649ece8883
  1. common/
  2. configurations/
  3. docs/
  4. fw-update/
  5. fw-update-legacy/
  6. host-bmc/
  7. libpldmresponder/
  8. oem/
  9. platform-mc/
  10. pldmd/
  11. pldmtool/
  12. requester/
  13. softoff/
  14. subprojects/
  15. test/
  16. tools/
  17. utilities/
  18. .clang-format
  19. .clang-tidy
  20. .eslintignore
  21. .gitignore
  22. .linter-ignore
  23. LICENSE
  24. meson.build
  25. meson.options
  26. OWNERS
  27. 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.