From: Max Reitz <mreitz@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 4/6] curl: Report only ready sockets
Date: Tue, 10 Sep 2019 09:53:23 +0200 [thread overview]
Message-ID: <a8894b10-113d-bde9-b3b1-35cea2a1ead7@redhat.com> (raw)
In-Reply-To: <6ecb6085-174f-f3a5-62cd-5a75a319c91f@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 2363 bytes --]
On 09.09.19 22:16, John Snow wrote:
>
>
> On 8/27/19 12:34 PM, Max Reitz wrote:
>> Instead of reporting all sockets to cURL, only report the one that has
>> caused curl_multi_do_locked() to be called. This lets us get rid of the
>> QLIST_FOREACH_SAFE() list, which was actually wrong: SAFE foreaches are
>> only safe when the current element is removed in each iteration. If it
>> possible for the list to be concurrently modified, we cannot guarantee
>> that only the current element will be removed. Therefore, we must not
>> use QLIST_FOREACH_SAFE() here.
>>
>> Fixes: ff5ca1664af85b24a4180d595ea6873fd3deac57
>> Cc: qemu-stable@nongnu.org
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>> block/curl.c | 17 ++++++-----------
>> 1 file changed, 6 insertions(+), 11 deletions(-)
>>
>> diff --git a/block/curl.c b/block/curl.c
>> index 05f77a38c2..bc70f39fcb 100644
>> --- a/block/curl.c
>> +++ b/block/curl.c
>> @@ -394,24 +394,19 @@ static void curl_multi_check_completion(BDRVCURLState *s)
>> }
>>
>> /* Called with s->mutex held. */
>> -static void curl_multi_do_locked(CURLSocket *ready_socket)
>> +static void curl_multi_do_locked(CURLSocket *socket)
>
> Only a momentary hiccup, then.
>
>> {
>> - CURLSocket *socket, *next_socket;
>> - CURLState *s = socket->state;
>> + BDRVCURLState *s = socket->state->s;
>> int running;
>> int r;
>>
>> - if (!s->s->multi) {
>> + if (!s->multi) {
>> return;
>> }
>>
>> - /* Need to use _SAFE because curl_multi_socket_action() may trigger
>> - * curl_sock_cb() which might modify this list */
>> - QLIST_FOREACH_SAFE(socket, &s->sockets, next, next_socket) {
>> - do {
>> - r = curl_multi_socket_action(s->s->multi, socket->fd, 0, &running);
>> - } while (r == CURLM_CALL_MULTI_PERFORM);
>> - }
>> + do {
>> + r = curl_multi_socket_action(s->multi, socket->fd, 0, &running);
>> + } while (r == CURLM_CALL_MULTI_PERFORM);
>> }
>>
>> static void curl_multi_do(void *arg)
>>
>
> We were just calling this spuriously on whatever sockets before?
Yep. I was to blame; but to my defense, before then we only called it
for a single socket (which doesn’t work that well for FTP).
Max
> Seems like a clear improvement, then.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-10 7:55 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 ` [Qemu-devel] [Qemu-block] " John Snow
2019-09-10 7:50 ` 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 [this message]
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=a8894b10-113d-bde9-b3b1-35cea2a1ead7@redhat.com \
--to=mreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@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).