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: Thu, 07 Apr 2022 11:39:58 +0000 [thread overview]
Message-ID: <bug-29022-10460-uE1cw9hqkH@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
----------------------------------------------------------------------------
Last reconfirmed| |2022-04-07
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at sourceware dot org |amerey at redhat dot com
--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
Aaron already wrote up a patch to use zero sized files as negative cache
instead of zero permission files:
https://sourceware.org/pipermail/elfutils-devel/2022q2/004861.html
The only question is how this works on upgrade with an old cache. But it might
just work out because the old negative cache files were also zero sized and the
unlink should just work despite any changes in permissions.
If someone could try it out and/or give it a formal review that would be great.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-07 11:39 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
2022-04-05 14:36 ` fche at redhat dot com
2022-04-07 11:39 ` mark at klomp dot org [this message]
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-uE1cw9hqkH@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).