From: John Snow <jsnow@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 2/6] curl: Keep *socket until the end of curl_sock_cb()
Date: Mon, 9 Sep 2019 16:09:24 -0400 [thread overview]
Message-ID: <4197624e-c06e-b7d9-4cf4-90af4ccc53cf@redhat.com> (raw)
In-Reply-To: <20190827163439.16686-3-mreitz@redhat.com>
On 8/27/19 12:34 PM, Max Reitz wrote:
> This does not really change anything, but it makes the code a bit easier
> to follow once we use @socket as the opaque pointer for
> aio_set_fd_handler().
>
> (Also, this change stops us from creating new CURLSocket objects when
> the cURL library just wants to stop listening on an existing socket that
> we do not recognize. With a well-behaving cURL, that should never
> happen anyway.)
>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> block/curl.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/block/curl.c b/block/curl.c
> index 92dc2f630e..8a45b371cc 100644
> --- a/block/curl.c
> +++ b/block/curl.c
> @@ -174,18 +174,16 @@ static int curl_sock_cb(CURL *curl, curl_socket_t fd, int action,
> if (socket->fd == fd) {
> if (action == CURL_POLL_REMOVE) {
> QLIST_REMOVE(socket, next);
> - g_free(socket);
> }
> break;
> }
> }
> - if (!socket) {
> + if (action != CURL_POLL_REMOVE && !socket) {
> socket = g_new0(CURLSocket, 1);
> socket->fd = fd;
> socket->state = state;
> QLIST_INSERT_HEAD(&state->sockets, socket, next);
> }
> - socket = NULL;
>
> trace_curl_sock_cb(action, (int)fd);
> switch (action) {
> @@ -207,6 +205,9 @@ static int curl_sock_cb(CURL *curl, curl_socket_t fd, int action,
> break;
> }
>
> + if (action == CURL_POLL_REMOVE) {
> + g_free(socket);
> + }
> return 0;
> }
>
>
Very naive question: why is CURL_POLL_REMOVE handled so early in the
function? Why not handle both QLIST_REMOVE and g_free under the
switch(action) construct entirely?
next prev parent reply other threads:[~2019-09-09 20:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 16:34 [Qemu-devel] [PATCH 0/6] block/curl: Fix hang and potential crash Max Reitz
2019-08-27 16:34 ` [Qemu-devel] [PATCH 1/6] curl: Keep pointer to the CURLState in CURLSocket Max Reitz
2019-09-09 20:05 ` [Qemu-devel] [Qemu-block] " John Snow
2019-08-27 16:34 ` [Qemu-devel] [PATCH 2/6] curl: Keep *socket until the end of curl_sock_cb() Max Reitz
2019-09-09 20:09 ` John Snow [this message]
2019-09-10 7:50 ` [Qemu-devel] [Qemu-block] " Max Reitz
2019-08-27 16:34 ` [Qemu-devel] [PATCH 3/6] curl: Pass CURLSocket to curl_multi_{do, read}() Max Reitz
2019-09-09 20:10 ` [Qemu-devel] [Qemu-block] " John Snow
2019-09-10 7:52 ` Max Reitz
2019-08-27 16:34 ` [Qemu-devel] [PATCH 4/6] curl: Report only ready sockets Max Reitz
2019-09-09 20:16 ` [Qemu-devel] [Qemu-block] " John Snow
2019-09-10 7:53 ` Max Reitz
2019-08-27 16:34 ` [Qemu-devel] [PATCH 5/6] curl: Handle success in multi_check_completion Max Reitz
2019-09-09 20:30 ` [Qemu-devel] [Qemu-block] " John Snow
2019-09-10 8:17 ` Max Reitz
2019-08-27 16:34 ` [Qemu-devel] [PATCH 6/6] curl: Check curl_multi_add_handle()'s return code Max Reitz
2019-09-09 20:32 ` [Qemu-devel] [Qemu-block] " John Snow
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=4197624e-c06e-b7d9-4cf4-90af4ccc53cf@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).