summaryrefslogtreecommitdiffstats
path: root/fs/fuse
diff options
context:
space:
mode:
authorMiklos Szeredi <mszeredi@suse.cz>2014-10-24 00:14:36 +0200
committerMiklos Szeredi <mszeredi@suse.cz>2014-10-24 00:14:36 +0200
commit787fb6bc9682ec7c05fb5d9561b57100fbc1cc41 (patch)
treefde11fbe9f87e95ef6078fcbfed5f55c9ba134f8 /fs/fuse
parentcbdf35bcb833bfd00f0925d7a9a33a21f41ea582 (diff)
downloadlinux-787fb6bc9682ec7c05fb5d9561b57100fbc1cc41.tar.bz2
vfs: add whiteout support
Whiteout isn't actually a new file type, but is represented as a char device (Linus's idea) with 0/0 device number. This has several advantages compared to introducing a new whiteout file type: - no userspace API changes (e.g. trivial to make backups of upper layer filesystem, without losing whiteouts) - no fs image format changes (you can boot an old kernel/fsck without whiteout support and things won't break) - implementation is trivial Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
Diffstat (limited to 'fs/fuse')
0 files changed, 0 insertions, 0 deletions