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)
committerDominique Martinet <dominique.martinet@cea.fr>
Tue, 3 Sep 2019 10:56:32 +0000 (10:56 +0000)
commitc87a37ebd40b889178664c2c09cc187334146292
treeb22de8286db49fc7416431010267f6267c161da4
parent089cf7f6ecb266b6a4164919a2e69bd2f938374a
9p: avoid attaching writeback_fid on mmap with type PRIVATE

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>
fs/9p/vfs_file.c