Searched hist:a19b6234410703c3b45d30636978e35f07f18394 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | host_notifier.hpp | diff a19b6234410703c3b45d30636978e35f07f18394 Thu Dec 12 13:30:14 CST 2019 Matt Spinler <spinler@us.ibm.com> PEL: Receive a 'bad PEL' indication from host
If the code somehow sent the host a malformed PEL, it will
respond with the 'Ack PEL' PLDM command with a special value
that indicates this, and the PLDM daemon will relay it to this
daemon.
In this case, change the host transmission state to 'bad' so
it doesn't get sent again. This should never happen as the
Repository class already validates PELs and removes bad ones,
though maybe the host and Repository have different ideas
about what constitutes a malformed PEL.
In the future, if event logging support is added to the PEL
code running inside the logging daemon, it may be a good
idea to create a new PEL for this case.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Id6f9fd37764bf5b5d09b4277a1e36b1f26b3e9a5
|
| H A D | host_notifier.cpp | diff a19b6234410703c3b45d30636978e35f07f18394 Thu Dec 12 13:30:14 CST 2019 Matt Spinler <spinler@us.ibm.com> PEL: Receive a 'bad PEL' indication from host
If the code somehow sent the host a malformed PEL, it will
respond with the 'Ack PEL' PLDM command with a special value
that indicates this, and the PLDM daemon will relay it to this
daemon.
In this case, change the host transmission state to 'bad' so
it doesn't get sent again. This should never happen as the
Repository class already validates PELs and removes bad ones,
though maybe the host and Repository have different ideas
about what constitutes a malformed PEL.
In the future, if event logging support is added to the PEL
code running inside the logging daemon, it may be a good
idea to create a new PEL for this case.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Id6f9fd37764bf5b5d09b4277a1e36b1f26b3e9a5
|
| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | host_notifier_test.cpp | diff a19b6234410703c3b45d30636978e35f07f18394 Thu Dec 12 13:30:14 CST 2019 Matt Spinler <spinler@us.ibm.com> PEL: Receive a 'bad PEL' indication from host
If the code somehow sent the host a malformed PEL, it will
respond with the 'Ack PEL' PLDM command with a special value
that indicates this, and the PLDM daemon will relay it to this
daemon.
In this case, change the host transmission state to 'bad' so
it doesn't get sent again. This should never happen as the
Repository class already validates PELs and removes bad ones,
though maybe the host and Repository have different ideas
about what constitutes a malformed PEL.
In the future, if event logging support is added to the PEL
code running inside the logging daemon, it may be a good
idea to create a new PEL for this case.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Id6f9fd37764bf5b5d09b4277a1e36b1f26b3e9a5
|