softmmu/physmem: file_ram_open() readonly improvements
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 46 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | softmmu/physmem: fallback to opening guest RAM file as readonly in a MAP_PRIVATE mappingsoftmmu/ | +18 | 43 replies | |
| 2/3 | softmmu/physmem: fail creation of new files in file_ram_open() with readonly=truesoftmmu/ | +7 | 0 replies | |
| 3/3 | softmmu/physmem: never return directories from file_ram_open()softmmu/ | +19 | 0 replies |
Reviews trailers per patch
None of the 3 patches has a Reviewed-by or Acked-by.
| Patch | Thiner Logoer |
|---|---|
| Series | T-b |
| 1/3 | |
| 2/3 | |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v1 0/3] softmmu/physmem: file_ram_open() readonly improvements
Patch #1 is the result of the discussion of:
"[PATCH v2] softmmu/physmem: try opening file readonly before failure
in file_ram_open" [1]
Instead of handling it inside file_ram_open(), handle it in the caller and only fallback to readonly in a MAP_PRIVATE mapping.
Patch #2 refuses to create readonly files instead of creating a new file and opening it writable. Patch #3 no longer returns directories from file_ram_open(), resulting in a better error message when trying to open a readonly file but specifying a directory.
[1] https://lkml.kernel.org/r/[email protected]
David Hildenbrand (2):
softmmu/physmem: fail creation of new files in file_ram_open() with
readonly=true
softmmu/physmem: never return directories from file_ram_open()
Thiner Logoer (1):
softmmu/physmem: fallback to opening guest RAM file as readonly in a
MAP_PRIVATE mapping
softmmu/physmem.c | 52 +++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 44 insertions(+), 8 deletions(-)
Signature · 1 line
2.41.0