From: Mark Wielaard <mark@klomp.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: PR27859 PATCH: correct 404-latch in connection reuse
Date: Sun, 16 May 2021 23:47:25 +0200 [thread overview]
Message-ID: <YKGS7bob7xKFxyOq@wildebeest.org> (raw)
In-Reply-To: <20210514225117.GA23897@redhat.com>
Hi Frank,
On Fri, May 14, 2021 at 06:51:17PM -0400, Frank Ch. Eigler via Elfutils-devel wrote:
> (I'll deploy this fix to one of the public servers to confirm it there.)
Thanks. If that looks good, please commit.
> Author: Frank Ch. Eigler <fche@redhat.com>
> Date: Fri May 14 18:37:30 2021 -0400
>
> PR27859: correct 404-latch bug in debuginfod client reuse
>
> PR27701 implemented curl handle reuse in debuginfod_client objects,
> but with an unexpected bug. Server responses returning an error
> "latched" because the curl_easy handles for error cases weren't all
> systematically removed from the curl multi handle. This prevented
> their proper re-addition the next time.
>
> This version of the code simplfies matters by making only the curl
> curl_multi handle long-lived. This turns out to be enough, because it
> can maintain a pool of long-lived http/https connections and related
> data, and lend them out to short-lived curl_easy handles. This mode
> handles errors or hung downloads even better, because the easy handles
> don't undergo complex state transitions between reuse.
>
> A new test case confirms this correction via the federating debuginfod
> instance (cleaning caches between subtests to make sure http* is being
> used and reused).
It is nice that the multi code works that way, it makes things a bit
simpler and less state to keep around for the debuginfod_client
handle. The changes look good to me. And the new testcase passes here.
Cheers,
Mark
next prev parent reply other threads:[~2021-05-16 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 22:51 Frank Ch. Eigler
2021-05-16 21:47 ` Mark Wielaard [this message]
2021-05-16 21:50 ` Frank Ch. Eigler
2021-05-17 10:08 ` Mark Wielaard
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=YKGS7bob7xKFxyOq@wildebeest.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).