diff options
| author | Brandon Maier <[email protected]> | 2020-12-17 17:19:18 -0600 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2021-04-16 11:55:55 -0400 |
| commit | b9c3052fbb25bff26702e6c16abfd0a5ec92040c (patch) | |
| tree | 6aa4cba91429f8c13bcb33c899c2739c388bb9ec /cmd/stackprot_test.c | |
| parent | bcb44f62b21e88cc74bc26939eb1dac95d2f430b (diff) | |
env: increment redund flag on read fail
If one of the reads fails when importing redundant environments (a
single read failure), the env_flags wouldn't get initialized in
env_import_redund(). If a user then calls saveenv, the new environment
will have the wrong flags value. So on the next load the new environment
will be ignored.
While debugging this, I also noticed that env/sf.c was not correctly
handling a single read failure, as it would not check the crc before
assigning it to gd->env_addr.
Having a special error path for when there is a single read failure
seems unnecessary and may lead to future bugs. Instead collapse the
'single read failure' error to be the same as a 'single crc failure'.
That way env_check_redund() either passes or fails, and if it passes we
are guaranteed to have checked the CRC.
Signed-off-by: Brandon Maier <[email protected]>
CC: Joe Hershberger <[email protected]>
CC: Wolfgang Denk <[email protected]>
CC: Heiko Schocher <[email protected]>
Reviewed-by: Tom Rini <[email protected]>
Diffstat (limited to 'cmd/stackprot_test.c')
0 files changed, 0 insertions, 0 deletions
