summaryrefslogtreecommitdiff
path: root/.gitattributes
diff options
context:
space:
mode:
authorBrandon Maier <brandon.maier@rockwellcollins.com>2020-12-18 02:19:18 +0300
committerTom Rini <trini@konsulko.com>2021-04-16 18:55:55 +0300
commitb9c3052fbb25bff26702e6c16abfd0a5ec92040c (patch)
tree6aa4cba91429f8c13bcb33c899c2739c388bb9ec /.gitattributes
parentbcb44f62b21e88cc74bc26939eb1dac95d2f430b (diff)
downloadu-boot-b9c3052fbb25bff26702e6c16abfd0a5ec92040c.tar.xz
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 <brandon.maier@rockwellcollins.com> CC: Joe Hershberger <joe.hershberger@ni.com> CC: Wolfgang Denk <wd@denx.de> CC: Heiko Schocher <hs@denx.de> Reviewed-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to '.gitattributes')
0 files changed, 0 insertions, 0 deletions