Skip to content

virtio-fs: Create a read-write mapping only if needed

Vivek Goyal virtio-fs 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest3 patches 3 repliesIn review
  2. v13 patches 7 repliesSuperseded

Changes in v2 from the cover letter

- 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.

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3fuse: Get rid of file parameter from setup mappingfs/fuse/file.c+7 -230 replies
2/3fuse: Move new mapping setup code in a functionfs/fuse/file.c+64 -520 replies
3/3fuse: Add logic to upgrade a read-only mapping to read-writefs/fuse/file.c fs/fuse/fuse_i.h+98 -263 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [Virtio-fs] [PATCH 0/3][V2] virtio-fs: Create a read-write mapping only if needed

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(-)
Signature · 1 line
2.17.2