summaryrefslogtreecommitdiff
path: root/firmware/3com
diff options
context:
space:
mode:
authorChao Yu <chao2.yu@samsung.com>2015-05-19 17:37:26 +0800
committerJaegeuk Kim <jaegeuk@kernel.org>2015-06-01 16:21:01 -0700
commit7e01e7ad746bc8198a8b46163ddc73a1c7d22339 (patch)
tree8a32ceb86167a410a450f98225ec63c9ebd63dce /firmware/3com
parent381722d2ac0314f65fd98db9a0eb8bdd1d984925 (diff)
f2fs: support RENAME_WHITEOUT
As the description of rename in manual, RENAME_WHITEOUT is a special operation that only makes sense for overlay/union type filesystem. When performing rename with RENAME_WHITEOUT, dst will be replace with src, and meanwhile, a 'whiteout' will be create with name of src. A "whiteout" is designed to be a char device with 0,0 device number, it has specially meaning for stackable filesystem. In these filesystems, there are multiple layers exist, and only top of these can be modified. So a whiteout in top layer is used to hide a corresponding file in lower layer, as well removal of whiteout will make the file appear. Now in overlayfs, when we rename a file which is exist in lower layer, it will be copied up to upper if it is not on upper layer yet, and then rename it on upper layer, source file will be whiteouted to hide corresponding file in lower layer at the same time. So in upper layer filesystem, implementation of RENAME_WHITEOUT provide a atomic operation for stackable filesystem to support rename operation. There are multiple ways to implement RENAME_WHITEOUT in log of this commit: 7dcf5c3e4527 ("xfs: add RENAME_WHITEOUT support") which pointed out by Dave Chinner. For now, we just try to follow the way that xfs/ext4 use. Signed-off-by: Chao Yu <chao2.yu@samsung.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'firmware/3com')
0 files changed, 0 insertions, 0 deletions