From: "amerey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27917] protect against federation loops
Date: Fri, 25 Jun 2021 18:59:21 +0000 [thread overview]
Message-ID: <bug-27917-10460-dWy17LcjSv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27917-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27917
Aaron Merey <amerey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amerey at redhat dot com
--- Comment #1 from Aaron Merey <amerey at redhat dot com> ---
Commit ab38d167c40c99 causes federation loops for non-existent resources to
result in multiple temporary livelocks, each lasting for $DEBUGINFOD_TIMEOUT
seconds. Since concurrent requests for each unique resource are now serialized,
federation loops can result in one server thread waiting to acquire a lock
while the server thread holding the lock waits for the first thread to respond
to an http request.
An implementation for this PR should help protect against this behaviour. Ex.
if --forwarded-ttl-limit=0 then the timeout behaviour of local loops should be
avoided.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-06-25 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 17:48 [Bug debuginfod/27917] New: " fche at redhat dot com
2021-06-08 14:13 ` [Bug debuginfod/27917] " dichen at redhat dot com
2021-06-25 18:59 ` amerey at redhat dot com [this message]
2021-08-26 3:04 ` dichen at redhat dot com
2021-08-27 17:43 ` mark at klomp dot org
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=bug-27917-10460-dWy17LcjSv@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).