public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug uprobes/28923] dtrace predictable temp file causes race
Date: Fri, 25 Feb 2022 02:07:21 +0000	[thread overview]
Message-ID: <bug-28923-6586-bKQ65Shtar@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28923-6586@http.sourceware.org/bugzilla/>

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

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fche at redhat dot com

--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
What do you think about using fcntl.flock() on the temp file, so as to lock out
other concurrent scripts?  (Additionally, it would be possible to salt the temp
file name with a function of the input .d content, so that it's reproducible
but not just a single common name.

-- 
You are receiving this mail because:
You are the assignee for the bug.

  reply	other threads:[~2022-02-25  2:07 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 ` fche at redhat dot com [this message]
2022-02-25 16:06 ` [Bug uprobes/28923] " 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
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-bKQ65Shtar@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).