From: "bugzilla at hadess dot net" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/29022] New: 000-permissions files cause problems for backups
Date: Mon, 04 Apr 2022 09:42:32 +0000 [thread overview]
Message-ID: <bug-29022-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29022
Bug ID: 29022
Summary: 000-permissions files cause problems for backups
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: bugzilla at hadess dot net
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
the debuginfod-client creates 000-permissions files as a way to mark "negative
caching". Unfortunately, that causes permissions problems for backup software,
disk usage checkers, etc. that rely on being able to access the user's own
files.
Given that the usage of those 000-permission files is not even atomic (see
commit 7d64173fb11c66284a408e52d41d15b7755d65d2), is there any reason not to
use the contents of the file, or the name of the file, or some other attribute
like the xattrs as a way to carry that "negative cache" information?
My backup software's log is hundreds of lines of:
Warning:
/home/hadess/.var/app/org.gnome.Totem.Devel/cache/debuginfod_client/d9ebf6de9e98f66a21daca59c8f601a9daa03c5b/debuginfo:
open: [Errno 13] Permission denied:
'/home/hadess/.var/app/org.gnome.Totem.Devel/cache/debuginfod_client/d9ebf6de9e98f66a21daca59c8f601a9daa03c5b/debuginfo'
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-04-04 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 9:42 bugzilla at hadess dot net [this message]
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
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@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).