From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Fiona Ebner <f.ebner@proxmox.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, quintela@redhat.com
Subject: Re: [PATCH] migration/channel-block: fix return value for qio_channel_block_{readv, writev}
Date: Wed, 12 Oct 2022 13:02:55 +0100 [thread overview]
Message-ID: <Y0asvufIM2hZgGau@redhat.com> (raw)
In-Reply-To: <20221012111935.117480-1-f.ebner@proxmox.com>
On Wed, Oct 12, 2022 at 01:19:35PM +0200, Fiona Ebner wrote:
> in the error case. The documentation in include/io/channel.h states
> that -1 or QIO_CHANNEL_ERR_BLOCK should be returned upon error. Simply
> passing along the return value from the bdrv-functions has the
> potential to confuse the call sides. Non-blocking mode is not
> implemented currently, so -1 it is.
Opps, yes, my bad in writing this code.
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> migration/channel-block.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/migration/channel-block.c b/migration/channel-block.c
> index c55c8c93ce..aabc4634a4 100644
> --- a/migration/channel-block.c
> +++ b/migration/channel-block.c
> @@ -62,7 +62,8 @@ qio_channel_block_readv(QIOChannel *ioc,
> qemu_iovec_init_external(&qiov, (struct iovec *)iov, niov);
> ret = bdrv_readv_vmstate(bioc->bs, &qiov, bioc->offset);
> if (ret < 0) {
> - return ret;
> + error_setg(errp, "bdrv_readv_vmstate returned error %d", ret);
IIUC, the bdrv functions return errno, so should use
error_setg_errno(errp, -ret, "bdrv_readv_vmstate returned error");
> bioc->offset += qiov.size;
> @@ -86,7 +87,8 @@ qio_channel_block_writev(QIOChannel *ioc,
> qemu_iovec_init_external(&qiov, (struct iovec *)iov, niov);
> ret = bdrv_writev_vmstate(bioc->bs, &qiov, bioc->offset);
> if (ret < 0) {
> - return ret;
> + error_setg(errp, "bdrv_writev_vmstate returned error %d", ret);
> + return -1;
> }
>
> bioc->offset += qiov.size;
> --
> 2.30.2
>
>
>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2022-10-12 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 11:19 [PATCH] migration/channel-block: fix return value for qio_channel_block_{readv, writev} Fiona Ebner
2022-10-12 11:35 ` Fiona Ebner
2022-10-12 12:02 ` Daniel P. Berrangé [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=Y0asvufIM2hZgGau@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=f.ebner@proxmox.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).