From: Manos Pitsidianakis <el13635@mail.ntua.gr>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/5] websock: Don't try to set *errp directly
Date: Thu, 8 Jun 2017 18:46:27 +0300 [thread overview]
Message-ID: <20170608154627.6nl5m4mzyrjdkfqn@postretch> (raw)
In-Reply-To: <20170608133906.12737-4-ehabkost@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On Thu, Jun 08, 2017 at 10:39:04AM -0300, Eduardo Habkost wrote:
>Assigning directly to *errp is not valid, as errp may be NULL,
>&error_fatal, or &error_abort. Use error_propagate() instead.
>
>Cc: "Daniel P. Berrange" <berrange@redhat.com>
>Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
>---
> io/channel-websock.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/io/channel-websock.c b/io/channel-websock.c
>index 8fabadea2f..5a3badbec2 100644
>--- a/io/channel-websock.c
>+++ b/io/channel-websock.c
>@@ -856,7 +856,7 @@ static ssize_t qio_channel_websock_readv(QIOChannel *ioc,
> ssize_t ret;
>
> if (wioc->io_err) {
>- *errp = error_copy(wioc->io_err);
>+ error_propagate(errp, error_copy(wioc->io_err));
> return -1;
> }
>
>@@ -902,7 +902,7 @@ static ssize_t qio_channel_websock_writev(QIOChannel *ioc,
> ssize_t ret;
>
> if (wioc->io_err) {
>- *errp = error_copy(wioc->io_err);
>+ error_propagate(errp, error_copy(wioc->io_err));
> return -1;
> }
>
>--
>2.11.0.259.g40922b1
>
>
>
Reviewed-by: Manos Pitsidianakis <el13635@mail.ntua.gr>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-08 15:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 13:39 [Qemu-devel] [PATCH 0/5] Error handling cleanup and fixes Eduardo Habkost
2017-06-08 13:39 ` [Qemu-devel] [PATCH 1/5] xilinx: Fix error handling Eduardo Habkost
2017-06-08 16:29 ` Alistair Francis
2017-07-05 11:44 ` Markus Armbruster
2017-07-06 14:08 ` Eduardo Habkost
2017-07-06 14:45 ` Markus Armbruster
2017-06-08 13:39 ` [Qemu-devel] [PATCH 2/5] block: Don't try to set *errp directly Eduardo Habkost
2017-06-08 15:04 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2017-07-05 11:50 ` [Qemu-devel] " Markus Armbruster
2017-06-08 13:39 ` [Qemu-devel] [PATCH 3/5] websock: " Eduardo Habkost
2017-06-08 15:46 ` Manos Pitsidianakis [this message]
2017-07-05 11:53 ` Markus Armbruster
2017-06-08 13:39 ` [Qemu-devel] [PATCH 4/5] migration: " Eduardo Habkost
2017-06-08 14:18 ` Juan Quintela
2017-06-08 14:21 ` Dr. David Alan Gilbert
2017-06-08 14:22 ` Dr. David Alan Gilbert
2017-06-08 13:39 ` [Qemu-devel] [PATCH 5/5] vnc: No need for Error** parameter at vnc_client_io_error() Eduardo Habkost
2017-06-08 15:17 ` Eric Blake
2017-06-08 16:05 ` Eduardo Habkost
2017-06-08 17:44 ` Eduardo Habkost
2017-06-08 21:22 ` Eric Blake
2017-06-08 15:18 ` [Qemu-devel] [PATCH 0/5] Error handling cleanup and fixes Eric Blake
2017-07-05 11:56 ` Markus Armbruster
2017-07-06 15:10 ` Markus Armbruster
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=20170608154627.6nl5m4mzyrjdkfqn@postretch \
--to=el13635@mail.ntua.gr \
--cc=armbru@redhat.com \
--cc=ehabkost@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).