From: "dannf at dannf dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/28923] dtrace predictable temp file causes race
Date: Sat, 26 Feb 2022 16:21:31 +0000 [thread overview]
Message-ID: <bug-28923-6586-m73uij68Mw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28923-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28923
--- Comment #5 from dann frazier <dannf at dannf dot org> ---
A hash of the contents - at least alone - would have the original problem I
think. In the libvirt case (and in my simple reproducer), the problem is that
we have 2 racing processes that are building the same target from the same
source in the same directory. So a hash of the contents of each would be the
same and still collide. We could add the contents into the hash *in addition
to* the filenames, but I don't think that would improve uniqueness.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-02-26 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 0:12 [Bug uprobes/28923] New: " dannf at dannf dot org
2022-02-25 2:07 ` [Bug uprobes/28923] " fche at redhat dot com
2022-02-25 16:06 ` dannf at dannf dot org
2022-02-25 23:29 ` dannf at dannf dot org
2022-02-26 1:14 ` fche at redhat dot com
2022-02-26 16:21 ` dannf at dannf dot org [this message]
2022-02-28 17:33 ` dannf at dannf dot org
2022-03-01 16:06 ` fche 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-28923-6586-m73uij68Mw@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).