u-boot.git/tools/env/fw_env.c, branch v2018.01

tools: env: Add support for direct read/write UBI volumes

2017-11-30T03:30:50Z

Up to now we were able to read/write environment data from/to UBI volumes only indirectly by gluebi driver. This driver creates NAND MTD on top of UBI volumes, which is quite a workaroung for this use case. Add support for direct read/write UBI volumes in order to not use obsolete gluebi driver. Forward-ported from this patch: http://patchwork.ozlabs.org/patch/619305/ Original patch: Signed-off-by: Marcin Niestroj Forward port: Signed-off-by: S. Lockwood-Childs

env: Remove CONFIG_ENV_AES support

2017-11-21T12:43:31Z

This support has been deprecated since v2017.09 due to security issues. We now remove this support. Signed-off-by: Tom Rini

env: Fix out of tree building of tools-all

2017-09-05T19:59:47Z

With the move of environment code from common/ to env/ a number of changes needed to be made to various make targets. We missed updating some of the files required for out of tree builds of the tools. Correct the 'environ' target to know that we need to work under tools/env/ still (not tools/environ/) and then update the wrappers in env_attr.c and env_flags.c to point to the new correct file. Reported-by: Peter Robinson Tested-by: Peter Robinson Signed-off-by: Tom Rini

fix: fw_env: Prevent writing error message on special files, which don't support fsync

2017-09-03T19:30:31Z

According to fsync specification [1] some special files (e.g., a pipe, FIFO, or socket) don't support synchronization and return either EROFS or EINVAL. On the linux side the sys_fsync -> do_fsync() checks if the requested file has f_op->fsync defined. If not it returns EINVAL [2]. This commit prevents writing error messages for files (devices), which do not support fsync(). [1] - http://man7.org/linux/man-pages/man2/fsync.2.html [2] - http://elixir.free-electrons.com/linux/v4.13-rc6/source/fs/sync.c#L183 Signed-off-by: Lukasz Majewski Acked-by: Michael Heimpold

env: Rename setenv() to env_set()

2017-08-16T12:22:18Z

We are now using an env_ prefix for environment functions. Rename setenv() for consistency. Also add function comments in common.h. Suggested-by: Wolfgang Denk Signed-off-by: Simon Glass

tools/fw_env: use fsync to ensure that data is physically stored

2017-07-22T19:36:16Z

Closing a file descriptor does not guarantee that the data has been successfully saved to disk, as the kernel might defer the write. Signed-off-by: Michael Heimpold

tools/env: avoid memory leak in fw_setenv

2017-04-18T14:29:22Z

If realloc fails we should release the old buffer. Signed-off-by: Heinrich Schuchardt Reviewed-by: Tom Rini Reviewed-by: Simon Glass

env: fix memory leak in fw_env routines

2017-04-12T17:28:29Z

fw_env_open allocates buffers to store the environment, but these buffers are never freed. This becomes quite nasty using the fw_ tools as library, because each access to the environment (even just reading a variable) generates a memory leak equal to the size of the environment. Fix this renaming fw_env_close() as fw_env_flush(), because the function really flushes the environment from RAM to storage, and add a fw_env_close function to free the allocated resources. Signed-off-by: Stefano Babic

env: split fw_env.h in public and private parts

2017-04-12T17:28:28Z

Move U-Boot private data into a separate file. This lets export fw_env.h to be used by external programs that want to change the environment using the library built in tools/env. Signed-off-by: Stefano Babic

tools/env: fix environment alignment tests for block devices

2016-11-28T20:10:36Z

commit 183923d3e412500bdc597d1745e2fb6f7f679ec7 enforces that the environment must start at an erase block boundary. For block devices the sample fw_env.config does not mandate a erase block size for block devices. A missing setting defaults to the full env size. Depending on the environment location the alignment check now errors out for perfectly legal settings. Fix this by defaulting to the standard blocksize of 0x200 for environments stored in a block device. That keeps the fw_env.config files for block devices working even with that new check. Signed-off-by: Max Krummenacher