From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: eblake@redhat.com, thuth@redhat.com, lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/1] libqtest: Improve error reporting for bad read from QEMU
Date: Fri, 17 Aug 2018 19:21:56 +0200 [thread overview]
Message-ID: <b3f06ed0-34f5-50e5-dcd6-fc3d22327408@redhat.com> (raw)
In-Reply-To: <20180815141945.10457-2-armbru@redhat.com>
On 15/08/2018 16:19, Markus Armbruster wrote:
> When read() from the qtest socket or the QMP socket fails or EOFs, we
> report "Broken pipe" and exit(1). This commonly happens when QEMU
> crashes. It also happens when QEMU refuses to run because the test
> passed it bad arguments. Sadly, we neglect to report either.
>
> Improve this by calling abort() instead of exit(1), so kill_qemu()
> runs, and reports how QEMU died. This improves error reporting to
> something like
>
> /x86_64/device/introspect/list: Broken pipe
> tests/libqtest.c:129: kill_qemu() detected QEMU death from signal 6 (Aborted) (dumped core)
>
> Three exit() remain in libqtest.c:
>
> * In qmp_response(), when we can't parse a QMP reply read from the QMP
> socket. Change to abort() for consistency.
>
> * In qtest_qemu_binary(), when QTEST_QEMU_BINARY isn't in the
> environment. This can only happen before we start QEMU. Leave
> alone.
>
> * In qtest_init_without_qmp_handshake(), when the fork()ed child fails
> to execlp(). Leave alone.
>
> exit() elsewhere are unlikely due to QEMU dying on us. If that should
> turn out to be wrong, we can move kill_qemu() from the abrt handler to
> atexit() or something.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> tests/libqtest.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tests/libqtest.c b/tests/libqtest.c
> index b703fca26d..852ccff1ce 100644
> --- a/tests/libqtest.c
> +++ b/tests/libqtest.c
> @@ -367,7 +367,7 @@ static GString *qtest_recv_line(QTestState *s)
>
> if (len == -1 || len == 0) {
> fprintf(stderr, "Broken pipe\n");
> - exit(1);
> + abort();
> }
>
> g_string_append_len(s->rx, buffer, len);
> @@ -454,7 +454,7 @@ static void qmp_response(JSONMessageParser *parser, GQueue *tokens)
> obj = json_parser_parse(tokens, NULL);
> if (!obj) {
> fprintf(stderr, "QMP JSON response parsing failed\n");
> - exit(1);
> + abort();
> }
>
> g_assert(!qmp->response);
> @@ -480,7 +480,7 @@ QDict *qmp_fd_receive(int fd)
>
> if (len == -1 || len == 0) {
> fprintf(stderr, "Broken pipe\n");
> - exit(1);
> + abort();
> }
>
> if (log) {
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2018-08-17 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 14:19 [Qemu-devel] [PATCH 0/1] libqtest: Improve error reporting for bad read from QEMU Markus Armbruster
2018-08-15 14:19 ` [Qemu-devel] [PATCH 1/1] " Markus Armbruster
2018-08-15 14:44 ` Philippe Mathieu-Daudé
2018-08-16 6:52 ` Markus Armbruster
2018-08-15 19:32 ` Eric Blake
2018-08-17 17:21 ` Paolo Bonzini [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=b3f06ed0-34f5-50e5-dcd6-fc3d22327408@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@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).