public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/29022] 000-permissions files cause problems for backups
Date: Mon, 04 Apr 2022 22:08:04 +0000	[thread overview]
Message-ID: <bug-29022-10460-ajpi7vsbjz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29022-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29022

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
Theoretically you can have a totally empty source files, but they are pretty
useless and they won't even leave any debug (DWARF) data (except for an empty
line table and compiler options string), so since there is no DWARF reference
to the source file it won't even be requested by any debuginfod consumer.
executables and debug files are ELF so are never zero size.

So I think it might make some sense to investigate whether we can use the fact
that a file is zero size as negative cache indicator. It would also get rid of
the "root is special" case.

At least I cannot imagine we really want to ever return a zero sized file. But
I might not have big enough imagination. There is always some theoretically
possibility that there is a legitimate request for a zero sized file in the
future. But do we really need to worry about that? Does it prevent some future
extensions?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  9:42 [Bug debuginfod/29022] New: " bugzilla at hadess dot net
2022-04-04 21:43 ` [Bug debuginfod/29022] " fche at redhat dot com
2022-04-04 22:08 ` mark at klomp dot org [this message]
2022-04-05 14:36 ` fche at redhat dot com
2022-04-07 11:39 ` mark at klomp dot org
2022-04-13 19:26 ` amerey at redhat dot com

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-29022-10460-ajpi7vsbjz@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).