From: Cornelia Huck <cohuck@redhat.com>
To: qemu-devel@nongnu.org
Cc: lvivier@redhat.com, berrange@redhat.com, peterx@redhat.com,
dgilbert@redhat.com, Cornelia Huck <cohuck@redhat.com>
Subject: [Qemu-devel] [PATCH] dump: do not dump non-existent guest memory
Date: Mon, 11 Sep 2017 15:26:27 +0200 [thread overview]
Message-ID: <20170911132627.9505-1-cohuck@redhat.com> (raw)
It does not really make sense to dump memory that is not there.
Moreover, that fixes a segmentation fault when calling dump-guest-memory
with no filter for a machine with no memory defined.
New behaviour is:
(qemu) dump-guest-memory /dev/null
dump: no guest memory to dump
(qemu) dump-guest-memory /dev/null 0 4096
dump: no guest memory to dump
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
---
Another unmaintained file. Joy. cc:ing some more-or-less random folks.
---
dump.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/dump.c b/dump.c
index a79773d0f7..d2093e141b 100644
--- a/dump.c
+++ b/dump.c
@@ -1536,6 +1536,12 @@ static void dump_init(DumpState *s, int fd, bool has_format,
fprintf(stderr, "DUMP: total memory to dump: %lu\n", s->total_size);
#endif
+ /* it does not make sense to dump non-existent memory */
+ if (!s->total_size) {
+ error_setg(errp, "dump: no guest memory to dump");
+ goto cleanup;
+ }
+
s->start = get_start_block(s);
if (s->start == -1) {
error_setg(errp, QERR_INVALID_PARAMETER, "begin");
--
2.13.5
next reply other threads:[~2017-09-11 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 13:26 Cornelia Huck [this message]
2017-09-11 13:45 ` [Qemu-devel] [PATCH] dump: do not dump non-existent guest memory Laurent Vivier
2017-09-11 14:02 ` Greg Kurz
2017-09-12 2:29 ` Peter Xu
2017-09-12 3:33 ` Peter Xu
2017-09-12 10:17 ` Marc-André Lureau
2017-09-13 6:12 ` Peter Xu
2017-09-13 7:58 ` Cornelia Huck
2017-09-14 5:40 ` Peter Xu
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=20170911132627.9505-1-cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=peterx@redhat.com \
--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).