From: "Andreas Färber" <afaerber@suse.de>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: famcool@gmail.com, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH] qtest: Don't segfault with invalid -qtest option
Date: Sat, 08 Feb 2014 15:27:49 +0100 [thread overview]
Message-ID: <52F63EE5.9000501@suse.de> (raw)
In-Reply-To: <20140208092838.epI9YAEbMFnJRt/M%famz@redhat.com>
Am 08.02.2014 10:28, schrieb Fam Zheng:
> This prints an error message, instead of core dump, when "-qtest"
> option value is invalid, e.g.:
>
> $ ./x86_64-softmmu/qemu-system-x86_64 -qtest unknown
> qemu-system-x86_64: Failed to initialize device for qtest: "unknown"
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
> include/sysemu/qtest.h | 2 +-
> qtest.c | 10 +++++++++-
> vl.c | 5 ++++-
> 3 files changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/include/sysemu/qtest.h b/include/sysemu/qtest.h
> index 112a661..fc108c7 100644
> --- a/include/sysemu/qtest.h
> +++ b/include/sysemu/qtest.h
> @@ -24,7 +24,7 @@ static inline bool qtest_enabled(void)
> }
>
> int qtest_init_accel(void);
> -void qtest_init(const char *qtest_chrdev, const char *qtest_log);
> +int qtest_init(const char *qtest_chrdev, const char *qtest_log);
>
> static inline int qtest_available(void)
> {
> diff --git a/qtest.c b/qtest.c
> index dcf1301..a037b3b 100644
> --- a/qtest.c
> +++ b/qtest.c
> @@ -19,6 +19,7 @@
> #include "hw/irq.h"
> #include "sysemu/sysemu.h"
> #include "sysemu/cpus.h"
> +#include "qemu/error-report.h"
>
> #define MAX_IRQ 256
>
> @@ -507,12 +508,18 @@ int qtest_init_accel(void)
> return 0;
> }
>
> -void qtest_init(const char *qtest_chrdev, const char *qtest_log)
> +int qtest_init(const char *qtest_chrdev, const char *qtest_log)
> {
> CharDriverState *chr;
>
> chr = qemu_chr_new("qtest", qtest_chrdev, NULL);
>
> + if (chr == NULL) {
> + error_report("Failed to initialize device for qtest: \"%s\"",
> + qtest_chrdev);
> + return -1;
> + }
> +
> qemu_chr_add_handlers(chr, qtest_can_read, qtest_read, qtest_event, chr);
> qemu_chr_fe_set_echo(chr, true);
>
> @@ -527,4 +534,5 @@ void qtest_init(const char *qtest_chrdev, const char *qtest_log)
> }
>
> qtest_chr = chr;
> + return 0;
> }
> diff --git a/vl.c b/vl.c
> index 383be1b..97ca823 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -4078,7 +4078,10 @@ int main(int argc, char **argv, char **envp)
> configure_accelerator();
>
> if (qtest_chrdev) {
> - qtest_init(qtest_chrdev, qtest_log);
> + int ret = qtest_init(qtest_chrdev, qtest_log);
> + if (ret) {
> + exit(1);
> + }
> }
>
> machine_opts = qemu_get_machine_opts();
Why don't you do the exit(1) in qtest_init()? Either that or keep void
and return an Error **errp so that you can print it here where the
exit(1) is.
Otherwise error_report() usage looks good.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2014-02-08 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 9:28 [Qemu-devel] [PATCH] qtest: Don't segfault with invalid -qtest option Fam Zheng
2014-02-08 14:27 ` Andreas Färber [this message]
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=52F63EE5.9000501@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=famcool@gmail.com \
--cc=famz@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).