From: Juan Quintela <quintela@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, peterx@redhat.com, famz@redhat.com,
peter.maydell@linaro.org, cohuck@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v2 6/6] migration: Route more error paths
Date: Wed, 27 Sep 2017 11:07:19 +0200 [thread overview]
Message-ID: <87fub8bjco.fsf@secure.laptop> (raw)
In-Reply-To: <20170925112917.21340-7-dgilbert@redhat.com> (David Alan Gilbert's message of "Mon, 25 Sep 2017 12:29:17 +0100")
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> 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 their own error paths need fixing.
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
But .....
> -void virtio_save(VirtIODevice *vdev, QEMUFile *f)
> +int virtio_save(VirtIODevice *vdev, QEMUFile *f)
> {
> BusState *qbus = qdev_get_parent_bus(DEVICE(vdev));
> VirtioBusClass *k = VIRTIO_BUS_GET_CLASS(qbus);
> @@ -1947,20 +1947,21 @@ void virtio_save(VirtIODevice *vdev, QEMUFile *f)
> }
>
> if (vdc->vmsd) {
> - vmstate_save_state(f, vdc->vmsd, vdev, NULL);
> + int ret = vmstate_save_state(f, vdc->vmsd, vdev, NULL);
> + if (ret) {
> + return ret;
> + }
> }
>
> /* Subsections */
> - vmstate_save_state(f, &vmstate_virtio, vdev, NULL);
> + return vmstate_save_state(f, &vmstate_virtio, vdev, NULL);
> }
We add error code, good.
>
> /* A wrapper for use as a VMState .put function */
> static int virtio_device_put(QEMUFile *f, void *opaque, size_t size,
> VMStateField *field, QJSON *vmdesc)
> {
> - virtio_save(VIRTIO_DEVICE(opaque), f);
> -
> - return 0;
> + return virtio_save(VIRTIO_DEVICE(opaque), f);
> }
And we add the error code. But are the callers ready to use it?
...
} else {
field->info->put(f, curr_elem, size, field, vmdesc_loop);
}
No, we need to fix it on the callers also. Yeap, that is can be fixed
in a posterios series.
Later, Juan.
next prev parent reply other threads:[~2017-09-27 9:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 11:29 [Qemu-devel] [PATCH v2 0/6] migration: let pre_save fail Dr. David Alan Gilbert (git)
2017-09-25 11:29 ` [Qemu-devel] [PATCH v2 1/6] migration: pre_save return int Dr. David Alan Gilbert (git)
2017-09-25 13:19 ` Richard Henderson
2017-09-25 13:25 ` Dr. David Alan Gilbert
2017-09-25 13:29 ` Richard Henderson
2017-09-26 2:31 ` Peter Xu
2017-09-26 13:27 ` Cornelia Huck
2017-09-27 8:57 ` Juan Quintela
2017-09-25 11:29 ` [Qemu-devel] [PATCH v2 2/6] migration: check pre_save return in vmstate_save_state Dr. David Alan Gilbert (git)
2017-09-26 2:36 ` Peter Xu
2017-09-26 13:29 ` Cornelia Huck
2017-09-27 8:58 ` Juan Quintela
2017-09-25 11:29 ` [Qemu-devel] [PATCH v2 3/6] migration: Check field save returns Dr. David Alan Gilbert (git)
2017-09-26 2:42 ` Peter Xu
2017-09-26 13:32 ` Cornelia Huck
2017-09-27 8:59 ` Juan Quintela
2017-09-25 11:29 ` [Qemu-devel] [PATCH v2 4/6] migration: wire vmstate_save_state errors up to vmstate_subsection_save Dr. David Alan Gilbert (git)
2017-09-26 2:45 ` Peter Xu
2017-09-26 9:55 ` Dr. David Alan Gilbert
2017-09-26 13:35 ` Cornelia Huck
2017-09-27 9:00 ` Juan Quintela
2017-09-25 11:29 ` [Qemu-devel] [PATCH v2 5/6] migration: Route errors up through vmstate_save Dr. David Alan Gilbert (git)
2017-09-26 2:56 ` Peter Xu
2017-09-26 13:36 ` Cornelia Huck
2017-09-27 9:00 ` Juan Quintela
2017-09-25 11:29 ` [Qemu-devel] [PATCH v2 6/6] migration: Route more error paths Dr. David Alan Gilbert (git)
2017-09-26 3:06 ` Peter Xu
2017-09-26 10:03 ` Dr. David Alan Gilbert
2017-09-26 13:39 ` Cornelia Huck
2017-09-27 9:07 ` Juan Quintela [this message]
2017-09-27 10:51 ` [Qemu-devel] [PATCH v2 0/6] migration: let pre_save fail Dr. David Alan Gilbert
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=87fub8bjco.fsf@secure.laptop \
--to=quintela@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.