From: "dale.hamel at srvthe dot net" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug releng/25581] USDT probes when /proc/[pid]/mem not writeable
Date: Thu, 20 Feb 2020 02:06:00 -0000 [thread overview]
Message-ID: <bug-25581-6586-C6dyyPKnbW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25581-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25581
--- Comment #1 from Dale Hamel <dale.hamel at srvthe dot net> ---
This is the first bug I have created on here, hopefully I have submitted it
correctly. If I am out of order at all, please direct me to the right way to
submit this issue / proposal for enhancement.
This patch has been tested in production and works around the dependency on a
semaphore for popular programs like ruby, memcached, mysql, and redis, and for
using USDT probes without impacting performance when not attached.
Thanks for taking the time to review this bug, I look forward to hearing your
feedback and suggestions,
-Dale
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-02-20 2:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 2:00 [Bug releng/25581] New: " dale.hamel at srvthe dot net
2020-02-20 2:02 ` [Bug releng/25581] " dale.hamel at srvthe dot net
2020-02-20 2:03 ` dale.hamel at srvthe dot net
2020-02-20 2:06 ` dale.hamel at srvthe dot net [this message]
2020-02-20 22:55 ` dale.hamel at srvthe dot net
2020-02-21 0:18 ` dale.hamel at srvthe dot net
2020-02-21 3:35 ` dale.hamel at srvthe dot net
2020-02-21 3:35 ` dale.hamel at srvthe dot net
2020-02-21 3:48 ` dale.hamel at srvthe dot net
2020-02-21 6:08 ` dale.hamel at srvthe dot net
2020-02-21 6:38 ` dale.hamel at srvthe dot net
2020-02-21 15:46 ` dale.hamel at srvthe dot net
2020-02-21 19:02 ` dale.hamel at srvthe dot net
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-25581-6586-C6dyyPKnbW@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).