From: Vivek Goyal Date: Fri, 26 Jul 2019 11:49:45 -0400 Message-Id: <20190726154948.28540-1-vgoyal@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [Virtio-fs] [PATCH 0/3][V2] virtio-fs: Create a read-write mapping only if needed List-Id: Development discussions about virtio-fs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: virtio-fs@redhat.com This is V2 of patches. Changes since V1: - Fixed the issue of dropping lock (liu bo) - Mapping could already be made writable by another thread after dropping read lock and acquiring write-lock. So check for that. Do not always create a read-write mapping. Create it read-write only if caller asked for it. Otherwise create a read-only mapping and upgrade it to read-write later when needed. Vivek Goyal (3): fuse: Get rid of file parameter from setup mapping fuse: Move new mapping setup code in a function fuse: Add logic to upgrade a read-only mapping to read-write fs/fuse/file.c | 253 +++++++++++++++++++++++++++++------------------ fs/fuse/fuse_i.h | 3 + 2 files changed, 162 insertions(+), 94 deletions(-) -- 2.17.2