From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>,
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: peter.maydell@linaro.org, quintela@redhat.com, cohuck@redhat.com,
qemu-devel@nongnu.org, peterx@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 5/5] migration: Route more error paths
Date: Wed, 20 Sep 2017 08:26:22 -0500 [thread overview]
Message-ID: <5b02462e-99c3-eb72-3481-93a26fc405e4@redhat.com> (raw)
In-Reply-To: <20170920035512.GF18491@lemon>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
On 09/19/2017 10:55 PM, Fam Zheng wrote:
> On Tue, 09/19 19:00, Dr. David Alan Gilbert (git) wrote:
>> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>>
>> vmstate_save is called in a few places, and vmstate_save_state is
>> called in lots of places.
>>
>> Route error returns from the easier cases back up; there are lots
>> of more complex cases where there own error paths need fixing.
>
>> +++ b/tests/test-vmstate.c
>> @@ -70,7 +70,7 @@ static void save_vmstate(const VMStateDescription *desc, void *obj)
>> QEMUFile *f = open_test_file(true);
>>
>> /* Save file with vmstate */
>> - vmstate_save_state(f, desc, obj, NULL);
>> + g_assert(!vmstate_save_state(f, desc, obj, NULL));
>
> Though this is test code, isn't putting anything with a side effect into an
> assert expression a very bad pattern in general?
Indeed - although we don't disable asserts (as of commit 262a69f4), this
should still be separated into running vmstate_save_state()
unconditionally, then asserting that the result stored into a temporary
variable matches expectations.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-09-20 13:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 18:00 [Qemu-devel] [PATCH 0/5] migration: let pre_save fail Dr. David Alan Gilbert (git)
2017-09-19 18:00 ` [Qemu-devel] [PATCH 1/5] migration: pre_save return int Dr. David Alan Gilbert (git)
2017-09-20 13:57 ` Cornelia Huck
2017-09-20 14:32 ` Dr. David Alan Gilbert
2017-09-19 18:00 ` [Qemu-devel] [PATCH 2/5] migration: check pre_save return in vmstate_save_state Dr. David Alan Gilbert (git)
2017-09-19 18:00 ` [Qemu-devel] [PATCH 3/5] migration: wire vmstate_save_state errors up to vmstate_subsection_save Dr. David Alan Gilbert (git)
2017-09-19 18:00 ` [Qemu-devel] [PATCH 4/5] migration: Route errors up through vmstate_save Dr. David Alan Gilbert (git)
2017-09-19 18:00 ` [Qemu-devel] [PATCH 5/5] migration: Route more error paths Dr. David Alan Gilbert (git)
2017-09-20 3:31 ` Peter Xu
2017-09-20 15:45 ` Dr. David Alan Gilbert
2017-09-20 3:55 ` Fam Zheng
2017-09-20 13:26 ` Eric Blake [this message]
2017-09-20 14:20 ` Dr. David Alan Gilbert
2017-09-20 15:32 ` Eric Blake
2017-09-20 14:30 ` Cornelia Huck
2017-09-20 15:57 ` Dr. David Alan Gilbert
2017-09-20 16:00 ` Cornelia Huck
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=5b02462e-99c3-eb72-3481-93a26fc405e4@redhat.com \
--to=eblake@redhat.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=famz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
/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).