From: Junio C Hamano <gitster@pobox.com>
To: szager@google.com
Cc: git@vger.kernel.org, sop@google.com
Subject: Re: Fix potential hang in https handshake (v2).
Date: Thu, 18 Oct 2012 17:33:54 -0700 [thread overview]
Message-ID: <7v8vb3l2q5.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <5080906b.xT6aRtW1ELoWhZZw%szager@google.com> (szager@google.com's message of "Thu, 18 Oct 2012 16:27:39 -0700")
szager@google.com writes:
> From aa77ab3dd5b98a5786ac158528f45355fc0ddbc3 Mon Sep 17 00:00:00 2001
> From: Stefan Zager <szager@google.com>
> Date: Thu, 18 Oct 2012 16:23:53 -0700
> Subject: [PATCH] Fix potential hang in https handshake.
Please don't do the above (as usual ;-)
> It will sometimes happen that curl_multi_fdset() doesn't
> return any file descriptors. In that case, it's recommended
> that the application sleep for a short time before running
> curl_multi_perform() again.
>
> http://curl.haxx.se/libcurl/c/curl_multi_fdset.html
>
> Signed-off-by: Stefan Zager <szager@google.com>
> ---
The above sounds like "the code is doing something against a
recommended practice", but is there a user-visible symptom due to
this?
We end up calling select() without any bit set in fds, so it would
become micro-sleep of select_timeout in such a case, but as far as I
can see, the existing code either
* does not select() and keeps polling step_active_slots() without
delay, when curl_timeout gives a 0 return value; or
* sets 50ms timeout or whatever negative value derived from
curl_timeout when the returned value is not 0 nor -1.
Is the symptom that select(), when given a negative timeout and no
fd to wake it, sleeps forever (or "loooong time, taking that negative
value as if it is a large unsigned long") or something?
Thanks.
> http.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/http.c b/http.c
> index df9bb71..e8aba7f 100644
> --- a/http.c
> +++ b/http.c
> @@ -630,6 +630,10 @@ void run_active_slot(struct active_request_slot *slot)
> FD_ZERO(&writefds);
> FD_ZERO(&excfds);
> curl_multi_fdset(curlm, &readfds, &writefds, &excfds, &max_fd);
> + if (max_fd < 0) {
> + select_timeout.tv_sec = 0;
> + select_timeout.tv_usec = 50000;
> + }
>
> select(max_fd+1, &readfds, &writefds, &excfds, &select_timeout);
> }
next prev parent reply other threads:[~2012-10-19 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 23:27 Fix potential hang in https handshake (v2) szager
2012-10-19 0:33 ` Junio C Hamano [this message]
2012-10-19 0:37 ` Junio C Hamano
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=7v8vb3l2q5.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sop@google.com \
--cc=szager@google.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