From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F16913858C62; Mon, 13 Mar 2023 16:40:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F16913858C62 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1678725648; bh=I0svSAuG5yLNh9nBwoJAdI+Wtlq+jn2cDTCatPV4pNk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=no3g33TaaDU2/9j6Nk9YqST2EKtxxHI40jsLn2XIUKJqAPTkKqGVFhbNJXissCO81 WvKRYafKxFDFT+VV0n79rahQ7WzxVAC3CiOwRDHEh+mUZGI5Dg/jsQxPgA8rmeuCHW FA5rrQzBaSoEfoGbnJbU43KLQRrSPOPBniThoFxE= From: "fche at redhat dot com" To: elfutils-devel@sourceware.org Subject: [Bug debuginfod/30221] Negative cache should differentiate failure types Date: Mon, 13 Mar 2023 16:40:48 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: elfutils X-Bugzilla-Component: debuginfod X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fche at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30221 Frank Ch. Eigler changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fche at redhat dot com --- Comment #1 from Frank Ch. Eigler --- Even a 404 error may be transient, as a server may just not have gotten aro= und to indexing new content yet. Other transient errors may persist awhile. I don't know of any unambiguous winning policy here. As to the question that, if such a policy were formulated, how could the results be represented in the filesystem: xattrs, yeah maybe. But even simpler would be to have the code set the mtime or ctime of the 0-length fi= le to a cause-related artificial timestamp that will inform the "cache_miss_s" expiry calculations. --=20 You are receiving this mail because: You are on the CC list for the bug.=