Chengguang Xu 18dd2b05f3 9p: avoid attaching writeback_fid on mmap with type PRIVATE ... [ Upstream commit c87a37ebd40b889178664c2c09cc187334146292 ] Currently on mmap cache policy, we always attach writeback_fid whether mmap type is SHARED or PRIVATE. However, in the use case of kata-container which combines 9p(Guest OS) with overlayfs(Host OS), this behavior will trigger overlayfs' copy-up when excute command inside container. Link: http://lkml.kernel.org/r/20190820100325.10313-1-cgxu519@zoho.com.cn Signed-off-by: Chengguang Xu <cgxu519@zoho.com.cn> Signed-off-by: Dominique Martinet <dominique.martinet@cea.fr> Signed-off-by: Sasha Levin <sashal@kernel.org>		2019-10-11 18:21:13 +02:00
..
acl.c	9p: acl: fix uninitialized iattr access	2019-07-03 13:14:42 +02:00
acl.h
cache.c	9p/cache.c: Fix memory leak in v9fs_cache_session_get_cookie	2019-10-07 18:57:29 +02:00
cache.h
fid.c
fid.h
Kconfig
Makefile
v9fs.c	9p locks: add mount option for lock retry interval	2019-04-20 09:16:00 +02:00
v9fs.h	9p locks: add mount option for lock retry interval	2019-04-20 09:16:00 +02:00
v9fs_vfs.h
vfs_addr.c	9p: pass the correct prototype to read_cache_page	2019-07-31 07:27:08 +02:00
vfs_dentry.c
vfs_dir.c
vfs_file.c	9p: avoid attaching writeback_fid on mmap with type PRIVATE	2019-10-11 18:21:13 +02:00
vfs_inode.c
vfs_inode_dotl.c
vfs_super.c
xattr.c
xattr.h