9p: avoid attaching writeback_fid on mmap with type PRIVATE
authorChengguang Xu <cgxu519@zoho.com.cn>
Tue, 20 Aug 2019 10:03:25 +0000 (18:03 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 11 Oct 2019 16:21:13 +0000 (18:21 +0200)
commit18dd2b05f349a3b430791b64676374a2d490896b
tree7966478ab9f07ca90c1de6060bfe5d67c9918d55
parent07f3596ce34484d99bbd1449381002b09b523528
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>
fs/9p/vfs_file.c