From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/29801] --monitor mode gets 2 hits to procfs("monitor_control").write for every 1 write
Date: Thu, 17 Nov 2022 19:38:55 +0000 [thread overview]
Message-ID: <bug-29801-6586-enTFTfwqVz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29801-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29801
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> ---
Nice analysis.
I suspect the problem originates from the setup_timeout() code that implements
the stap -T NNN function. Its join_group etc. stuff was probably buggy, and
was copy-pasted into the monitor-related synthetic probe stuff.
I think the right fix there is to drop the dp->join_group(s); in each of those
clones, because synthetic derived_probe objects are joined at the other area
you found.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-11-17 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 19:19 [Bug translator/29801] New: " rgoldber at redhat dot com
2022-11-17 19:38 ` fche at redhat dot com [this message]
2022-11-18 15:58 ` [Bug translator/29801] " rgoldber 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-29801-6586-enTFTfwqVz@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).