coredump-config: Move to tmpfs in ExecStopPost

Currently, the coredump-config service is configured to only move files
to tmpfs if the service has already started up successfully. If you try
to stop the service before it's done starting up, the ExecStop command
won't run, which leaves a dangling reference to the eMMC LUKS device,
and as a result, we can't deactivate the LUKS device.

This commit changes the ExecStop entry to an ExecStopPost entry, so that
command will run regardless of whether the startup was successful, and
regardless of whether the startup already finished.

Tested:
Repeatedly formatted and immediately locked the eMMC 500 times.

presubmit:
https://fusion2.corp.google.com/fcdced94-95f1-3ff2-a06b-e1b3a1586d8e
https://fusion2.corp.google.com/e1215315-822e-317f-b6ef-2a24f6b62d8a
https://fusion2.corp.google.com/ae767654-243f-317a-9904-10c872880a7e
https://fusion2.corp.google.com/0533ae54-a36d-3cd3-adb8-6ecc7d3ea6fc

Google-Bug-Id: 385091808
Google-Bug-Id: 363092253
Google-Bug-Id: 384881453
Change-Id: Ied662705160dff040af8d101931a632af817c435
Signed-off-by: John Wedig <johnwedig@google.com>
1 file changed
tree: 4886aec223458ba2576032a5327db0422f2acdfa
  1. classes/
  2. conf/
  3. dynamic-layers/
  4. recipes-bsp/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-google/
  10. recipes-kernel/
  11. recipes-phosphor/
  12. recipes-support/
  13. recipes-tpm1/
  14. recipes-tpm2/
  15. LICENSE
  16. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.