emmc_log: Fix exit condition on vacuum logs

The logic used to check for `req_size > perst_size` then exit, however,
this means that the the persistent size left over in eMMC after dumping
run/logs is greater than the current persistent log usage. It should be
checking for less than, because that would mean the free persistent size
doesn't fix the run/logs.

This can lead to a corner cases where we never exit the loop.
Refactor the check to clear up the confusion.

Tested:
|-------total-------|
|--free--|---used---|
|--run--|

if run + 1M > free, then we can't dump the log and exit.

Google-Bug-Id: 299976757
Change-Id: Ie783dbda6aeb707932c318c66dabcdb6dd0e3086
Signed-off-by: Willy Tu <wltu@google.com>
1 file changed
tree: a4ab3f2643ac40e41f81813b8e45ec89c318082f
  1. conf/
  2. dynamic-layers/
  3. recipes-bsp/
  4. recipes-connectivity/
  5. recipes-core/
  6. recipes-devtools/
  7. recipes-extended/
  8. recipes-google/
  9. recipes-kernel/
  10. recipes-phosphor/
  11. recipes-tpm1/
  12. LICENSE
  13. 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.