Summary: | reused debuginfod_client objects don't clean out curl handles enough | ||
---|---|---|---|
Product: | elfutils | Reporter: | Frank Ch. Eigler <fche> |
Component: | debuginfod | Assignee: | Frank Ch. Eigler <fche> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | elfutils-devel |
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
See Also: | https://sourceware.org/bugzilla/show_bug.cgi?id=27701 | ||
Host: | Target: | ||
Build: | Last reconfirmed: |
Description
Frank Ch. Eigler
2021-05-13 01:26:42 UTC
On Thu, May 13, 2021 at 01:26:42AM +0000, fche at redhat dot com via Elfutils-devel wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=27859 > > In a sequence of queries on the same debuginfod_client, as long as > they are all successful, things are fine. Once there is a 404 error > however, this appears to latch, and subsequent requests give 404 > whether or not they were resolvable by upstream. Makes sense that curl remembers 404 results. Does that mean we need to refresh the curl handle when a request is made for a negative cached entry and cache_miss_s expires? commit 0b454c7e1997 fixes this. |