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.
Date: Thu, 18 Oct 2012 15:59:41 -0700 [thread overview]
Message-ID: <7vd30fl736.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <5080761e.IEDySUuQzlCwL6fM%szager@google.com> (szager@google.com's message of "Thu, 18 Oct 2012 14:35:26 -0700")
szager@google.com writes:
> From 700b8075c578941c8f951711825c390ac68b190f Mon Sep 17 00:00:00 2001
> From: Stefan Zager <szager@google.com>
> Date: Thu, 18 Oct 2012 14:03:59 -0700
> Subject: [PATCH] Fix potential hang in https handshake.
>
> 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>
> ---
Thanks. Would it be a better idea to "patch up" in problematic
case, instead of making this logic too deeply nested, like this
instead, I have to wonder...
... all the existing code above unchanged ...
curl_multi_fdset(..., &max_fd);
+ if (max_fd < 0) {
+ /* nothing actionable??? */
+ select_timeout.tv_sec = 0;
+ select_timeout.tv_usec = 50000;
+ }
select(max_fd+1, ..., &select_timeout);
> http.c | 40 ++++++++++++++++++++++++++--------------
> 1 files changed, 26 insertions(+), 14 deletions(-)
>
> diff --git a/http.c b/http.c
> index df9bb71..a6f66c0 100644
> --- a/http.c
> +++ b/http.c
> @@ -602,35 +602,47 @@ void run_active_slot(struct active_request_slot *slot)
> int max_fd;
> struct timeval select_timeout;
> int finished = 0;
> + long curl_timeout;
>
> slot->finished = &finished;
> while (!finished) {
> step_active_slots();
>
> if (slot->in_use) {
> + max_fd = -1;
> + FD_ZERO(&readfds);
> + FD_ZERO(&writefds);
> + FD_ZERO(&excfds);
> + curl_multi_fdset(curlm, &readfds, &writefds, &excfds, &max_fd);
> +
> #if LIBCURL_VERSION_NUM >= 0x070f04
> - long curl_timeout;
> - curl_multi_timeout(curlm, &curl_timeout);
> - if (curl_timeout == 0) {
> - continue;
> - } else if (curl_timeout == -1) {
> + /* 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
> + */
> + if (max_fd == -1) {
> select_timeout.tv_sec = 0;
> select_timeout.tv_usec = 50000;
> } else {
> - select_timeout.tv_sec = curl_timeout / 1000;
> - select_timeout.tv_usec = (curl_timeout % 1000) * 1000;
> + curl_timeout = 0;
> + curl_multi_timeout(curlm, &curl_timeout);
> + if (curl_timeout == 0) {
> + continue;
> + } else if (curl_timeout == -1) {
> + select_timeout.tv_sec = 0;
> + select_timeout.tv_usec = 50000;
> + } else {
> + select_timeout.tv_sec = curl_timeout / 1000;
> + select_timeout.tv_usec = (curl_timeout % 1000) * 1000;
> + }
> }
> #else
> select_timeout.tv_sec = 0;
> select_timeout.tv_usec = 50000;
> #endif
> -
> - max_fd = -1;
> - FD_ZERO(&readfds);
> - FD_ZERO(&writefds);
> - FD_ZERO(&excfds);
> - curl_multi_fdset(curlm, &readfds, &writefds, &excfds, &max_fd);
> -
> select(max_fd+1, &readfds, &writefds, &excfds, &select_timeout);
> }
> }
next prev parent reply other threads:[~2012-10-18 22:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 21:35 Fix potential hang in https handshake szager
2012-10-18 22:59 ` Junio C Hamano [this message]
2012-10-19 10:36 ` Jeff King
2012-10-19 14:10 ` Shawn Pearce
[not found] ` <CAHOQ7J9W8FdKqzqbuDqj4bcFyN02kUigWtbL_xCen-PYWF9LUg@mail.gmail.com>
2012-10-19 17:02 ` Junio C Hamano
2012-10-19 17:08 ` Daniel Stenberg
2012-10-19 20:27 ` Jeff King
2012-10-19 20:37 ` Stefan Zager
2012-10-19 20:40 ` Jeff King
2012-10-19 20:40 ` 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=7vd30fl736.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;
as well as URLs for NNTP newsgroup(s).