For environments stored on filesystems where you can't have a redundant configuration, rather than just over-writing the existing environment in fw_setenv, do the tradtional create temporary file, rename, sync, sync directory dance to achieve ACID semantics when writing through fw_setenv.
Note that this series triggers large numbers of checkpatch warnings because of the existing code style:
warning: space prohibited between function name and open parenthesis '(' check: Avoid CamelCase: <HaveRedundEnv>
Alex Kiernan (2): tools: env: Refactor write path of flash_io() tools: env: Implement atomic replace for filesystem
tools/env/fw_env.c | 159 ++++++++++++++++++++++++++++++++++++++++------------- 1 file changed, 121 insertions(+), 38 deletions(-)