From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P . Berrange" <berrange@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
Thomas Huth <thuth@redhat.com>,
qemu-arm@nongnu.org, qemu-ppc@nongnu.org,
Peter Maydell <peter.maydell@linaro.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Greg Kurz <groug@kaod.org>, Laurent Vivier <lvivier@redhat.com>
Subject: [Qemu-devel] [PATCH v3 2/3] hmp: fix "dump-quest-memory" segfault (arm)
Date: Tue, 12 Sep 2017 16:01:48 +0200 [thread overview]
Message-ID: <20170912140149.7692-3-lvivier@redhat.com> (raw)
In-Reply-To: <20170912140149.7692-1-lvivier@redhat.com>
Running QEMU with
qemu-system-aarch64 -M none -nographic -m 256
and executing
dump-guest-memory /dev/null 0 8192
results in segfault
Fix by checking if we have CPU, and exit with
error if there is no CPU:
(qemu) dump-guest-memory /dev/null
this feature or command is not currently supported
Signed-off-by: Laurent Vivier <lvivier@redhat.com>
---
target/arm/arch_dump.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/target/arm/arch_dump.c b/target/arm/arch_dump.c
index 1a9861f69b..9e5b2fb31c 100644
--- a/target/arm/arch_dump.c
+++ b/target/arm/arch_dump.c
@@ -273,11 +273,18 @@ int arm_cpu_write_elf32_note(WriteCoreDumpFunction f, CPUState *cs,
int cpu_get_dump_info(ArchDumpInfo *info,
const GuestPhysBlockList *guest_phys_blocks)
{
- ARMCPU *cpu = ARM_CPU(first_cpu);
- CPUARMState *env = &cpu->env;
+ ARMCPU *cpu;
+ CPUARMState *env;
GuestPhysBlock *block;
hwaddr lowest_addr = ULLONG_MAX;
+ if (first_cpu == NULL) {
+ return -1;
+ }
+
+ cpu = ARM_CPU(first_cpu);
+ env = &cpu->env;
+
/* Take a best guess at the phys_base. If we get it wrong then crash
* will need '--machdep phys_offset=<phys-offset>' added to its command
* line, which isn't any worse than assuming we can use zero, but being
--
2.13.5
next prev parent reply other threads:[~2017-09-12 14:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 14:01 [Qemu-devel] [PATCH v3 0/3] hmp: fix "dump-quest-memory" segfault Laurent Vivier
2017-09-12 14:01 ` [Qemu-devel] [PATCH v3 1/3] hmp: fix "dump-quest-memory" segfault (ppc) Laurent Vivier
2017-09-12 14:10 ` Thomas Huth
2017-09-12 14:48 ` Greg Kurz
2017-09-13 5:35 ` David Gibson
2017-09-13 12:44 ` Dr. David Alan Gilbert
2017-09-13 12:48 ` Cornelia Huck
2017-09-13 12:49 ` Laurent Vivier
2017-09-13 13:19 ` Dr. David Alan Gilbert
2017-09-13 13:23 ` Laurent Vivier
2017-09-13 13:40 ` Dr. David Alan Gilbert
2017-09-13 12:54 ` David Gibson
2017-09-12 14:01 ` Laurent Vivier [this message]
2017-09-12 14:11 ` [Qemu-devel] [PATCH v3 2/3] hmp: fix "dump-quest-memory" segfault (arm) Thomas Huth
2017-09-12 14:50 ` Greg Kurz
2017-09-12 14:01 ` [Qemu-devel] [PATCH v3 3/3] tests/hmp: test "none" machine with memory Laurent Vivier
2017-09-12 14:13 ` Thomas Huth
2017-09-13 7:53 ` Cornelia Huck
2017-09-12 14:17 ` [Qemu-devel] [PATCH v3 0/3] hmp: fix "dump-quest-memory" segfault no-reply
2017-09-12 14:46 ` Greg Kurz
2017-09-12 14:51 ` Thomas Huth
2017-09-12 15:26 ` Greg Kurz
2017-09-12 15:36 ` Dr. David Alan Gilbert
2017-09-13 5:34 ` David Gibson
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=20170912140149.7692-3-lvivier@redhat.com \
--to=lvivier@redhat.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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).