public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Milian Wolff <mail@milianw.de>
Cc: Aaron Merey <amerey@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: caching failed lookups of debuginfo?
Date: Sat, 9 Apr 2022 00:21:08 +0200	[thread overview]
Message-ID: <YlC1VJKFnBIfYb4h@wildebeest.org> (raw)
In-Reply-To: <2180828.1FMjDaRedj@milian-workstation>

Hi Milian,

On Fri, Apr 08, 2022 at 11:56:15PM +0200, Milian Wolff wrote:
> Which in turn points at the code that does cache cleanup in 
> `debuginfod_query_server`. I now used `rr` to record such a bogus run and I 
> clearly see that `(time(NULL) - st.st_mtime <= cache_miss)` is false and it 
> goes into the unlink case.
> 
> I'll try to debug this further now - I definitely do not wait 600s inbetween 
> these runs here...

I can replicate this on an debian system with /home on ext4.  st_mtime
doesn't seem to change ever. When the file is created the st_mtime
seems to be in the past. So time(NULL) - st.st_mtime <= cache_miss is
always false. I am not sure why yet.

Cheers,

Mark


  reply	other threads:[~2022-04-08 22:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 19:58 Milian Wolff
2022-04-08 20:05 ` Frank Ch. Eigler
2022-04-08 20:45   ` Milian Wolff
2022-04-08 20:59     ` Mark Wielaard
2022-04-08 21:08       ` Milian Wolff
2022-04-08 21:34         ` Aaron Merey
2022-04-08 21:56           ` Milian Wolff
2022-04-08 22:21             ` Mark Wielaard [this message]
2022-04-08 22:23             ` Milian Wolff
2022-04-08 22:40               ` Mark Wielaard
2022-04-08 22:54                 ` Aaron Merey

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=YlC1VJKFnBIfYb4h@wildebeest.org \
    --to=mark@klomp.org \
    --cc=amerey@redhat.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=mail@milianw.de \
    /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).