From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27711] New: grooming should process -I/-X
Date: Thu, 08 Apr 2021 15:58:20 +0000 [thread overview]
Message-ID: <bug-27711-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27711
Bug ID: 27711
Summary: grooming should process -I/-X
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: fche at redhat dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
The debuginfod -I/-X regexes operate during traversal to identify those files
in need of scanning. The regexes are not used during grooming. This means
that if from run to run, the regex changes so that formerly indexed files are
excluded from traversal, the data is still retained in the index.
This is both good and bad. On one hand, if the underlying data is still
available, grooming will preserve the data, and let clients ask for it. On the
other hand, if the growing index size is a problem, and one wishes to age
no-longer-regex-matching index data out, there is no way.
Let's add a debuginfod flag to use regexes during grooming. Specifically, in
groom(), where the stat() test exists, also check for regex matching as in
scan_source_paths(). Treat failure of the regex the same way as though the
file didn't exist.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-04-08 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 15:58 fche at redhat dot com [this message]
2021-05-25 17:27 ` [Bug debuginfod/27711] " nsanci at redhat dot com
2021-07-09 13:58 ` 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-27711-10460@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).