virtio-fs: Create a read-write mapping only if needed
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest3 patches 3 repliesIn review
- 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 files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | fuse: Get rid of file parameter from setup mappingfs/ | +7 | 0 replies | |
| 2/3 | fuse: Move new mapping setup code in a functionfs/ | +64 | 0 replies | |
| 3/3 | fuse: Add logic to upgrade a read-only mapping to read-writefs/ fs/ | +98 | 3 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
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