From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: "David Hildenbrand" <david@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Thiner Logoer" <logoerthiner1@163.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v1 1/3] softmmu/physmem: fallback to opening guest RAM file as readonly in a MAP_PRIVATE mapping
Date: Mon, 7 Aug 2023 21:07:32 +0200 [thread overview]
Message-ID: <20230807190736.572665-2-david@redhat.com> (raw)
In-Reply-To: <20230807190736.572665-1-david@redhat.com>
From: Thiner Logoer <logoerthiner1@163.com>
Users may specify
* "-mem-path" or
* "-object memory-backend-file,share=off,readonly=off"
and expect such COW (MAP_PRIVATE) mappings to work, even if the user
does not have write permissions to open the file.
For now, we would always fail in that case, always requiring file write
permissions. Let's detect when that failure happens and fallback to opening
the file readonly.
Warn the user, since there are other use cases where we want the file to
be mapped writable: ftruncate() and fallocate() will fail if the file
was not opened with write permissions.
Signed-off-by: Thiner Logoer <logoerthiner1@163.com>
Co-developed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
---
softmmu/physmem.c | 26 ++++++++++++++++++--------
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/softmmu/physmem.c b/softmmu/physmem.c
index 3df73542e1..d1ae694b20 100644
--- a/softmmu/physmem.c
+++ b/softmmu/physmem.c
@@ -1289,8 +1289,7 @@ static int64_t get_file_align(int fd)
static int file_ram_open(const char *path,
const char *region_name,
bool readonly,
- bool *created,
- Error **errp)
+ bool *created)
{
char *filename;
char *sanitized_name;
@@ -1334,10 +1333,7 @@ static int file_ram_open(const char *path,
g_free(filename);
}
if (errno != EEXIST && errno != EINTR) {
- error_setg_errno(errp, errno,
- "can't open backing store %s for guest RAM",
- path);
- return -1;
+ return -errno;
}
/*
* Try again on EINTR and EEXIST. The latter happens when
@@ -1946,9 +1942,23 @@ RAMBlock *qemu_ram_alloc_from_file(ram_addr_t size, MemoryRegion *mr,
bool created;
RAMBlock *block;
- fd = file_ram_open(mem_path, memory_region_name(mr), readonly, &created,
- errp);
+ fd = file_ram_open(mem_path, memory_region_name(mr), readonly, &created);
+ if (fd == -EACCES && !(ram_flags & RAM_SHARED) && !readonly) {
+ /*
+ * We can have a writable MAP_PRIVATE mapping of a readonly file.
+ * However, some operations like ftruncate() or fallocate() might fail
+ * later, let's warn the user.
+ */
+ fd = file_ram_open(mem_path, memory_region_name(mr), true, &created);
+ if (fd >= 0) {
+ warn_report("backing store %s for guest RAM (MAP_PRIVATE) opened"
+ " readonly because the file is not writable", mem_path);
+ }
+ }
if (fd < 0) {
+ error_setg_errno(errp, -fd,
+ "can't open backing store %s for guest RAM",
+ mem_path);
return NULL;
}
--
2.41.0
next prev parent reply other threads:[~2023-08-07 19:08 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 19:07 [PATCH v1 0/3] softmmu/physmem: file_ram_open() readonly improvements David Hildenbrand
2023-08-07 19:07 ` David Hildenbrand [this message]
2023-08-08 21:01 ` [PATCH v1 1/3] softmmu/physmem: fallback to opening guest RAM file as readonly in a MAP_PRIVATE mapping Peter Xu
2023-08-09 5:39 ` ThinerLogoer
2023-08-09 9:20 ` David Hildenbrand
2023-08-09 15:15 ` Peter Xu
2023-08-10 14:19 ` David Hildenbrand
2023-08-10 17:06 ` ThinerLogoer
2023-08-10 21:24 ` Peter Xu
2023-08-11 5:49 ` ThinerLogoer
2023-08-11 14:31 ` Peter Xu
2023-08-12 6:21 ` ThinerLogoer
2023-08-22 13:35 ` David Hildenbrand
2023-08-11 19:00 ` David Hildenbrand
2023-08-12 5:18 ` ThinerLogoer
2023-08-17 9:07 ` David Hildenbrand
2023-08-17 14:30 ` David Hildenbrand
2023-08-17 14:37 ` Daniel P. Berrangé
2023-08-17 14:37 ` David Hildenbrand
2023-08-17 14:45 ` Daniel P. Berrangé
2023-08-17 14:47 ` David Hildenbrand
2023-08-17 14:41 ` Peter Xu
2023-08-17 15:02 ` David Hildenbrand
2023-08-17 15:13 ` Stefan Hajnoczi
2023-08-17 15:15 ` David Hildenbrand
2023-08-17 15:25 ` David Hildenbrand
2023-08-17 15:31 ` Peter Xu
2023-08-17 15:43 ` David Hildenbrand
2023-08-17 13:46 ` Daniel P. Berrangé
2023-08-17 13:48 ` David Hildenbrand
2023-08-11 14:59 ` David Hildenbrand
2023-08-11 15:26 ` David Hildenbrand
2023-08-11 16:16 ` Peter Xu
2023-08-11 16:17 ` David Hildenbrand
2023-08-11 16:22 ` Peter Xu
2023-08-11 16:25 ` David Hildenbrand
2023-08-11 16:54 ` Peter Xu
2023-08-11 17:39 ` David Hildenbrand
2023-08-11 21:07 ` Peter Xu
2023-08-21 12:20 ` Igor Mammedov
2023-08-11 15:47 ` Peter Xu
2023-08-17 13:42 ` Daniel P. Berrangé
2023-08-17 13:45 ` David Hildenbrand
2023-08-17 13:37 ` Daniel P. Berrangé
2023-08-17 13:44 ` David Hildenbrand
2023-08-07 19:07 ` [PATCH v1 2/3] softmmu/physmem: fail creation of new files in file_ram_open() with readonly=true David Hildenbrand
2023-08-07 19:07 ` [PATCH v1 3/3] softmmu/physmem: never return directories from file_ram_open() David Hildenbrand
2023-08-08 17:26 ` Re:[PATCH v1 0/3] softmmu/physmem: file_ram_open() readonly improvements ThinerLogoer
2023-08-10 11:11 ` [PATCH " Philippe Mathieu-Daudé
2023-08-10 16:35 ` ThinerLogoer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230807190736.572665-2-david@redhat.com \
--to=david@redhat.com \
--cc=imammedo@redhat.com \
--cc=logoerthiner1@163.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).