Searched +hist:787 +hist:fb6bc (Results 1 - 2 of 2) sorted by relevance
| /linux-master/fs/ | ||
| H A D | namei.c | diff 787fb6bc Thu Oct 23 16:14:36 MDT 2014 Miklos Szeredi <mszeredi@suse.cz> 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> diff 787fb6bc Thu Oct 23 16:14:36 MDT 2014 Miklos Szeredi <mszeredi@suse.cz> 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> |
| /linux-master/include/linux/ | ||
| H A D | fs.h | diff 787fb6bc Thu Oct 23 16:14:36 MDT 2014 Miklos Szeredi <mszeredi@suse.cz> 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> diff 787fb6bc Thu Oct 23 16:14:36 MDT 2014 Miklos Szeredi <mszeredi@suse.cz> 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> |
Completed in 1320 milliseconds