From: "mhiramat at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/6932] c->busy can be removed from kprobe-based handlers
Date: Wed, 01 Oct 2008 20:57:00 -0000 [thread overview]
Message-ID: <20081001205641.10464.qmail@sourceware.org> (raw)
In-Reply-To: <20081001203800.6932.mhiramat@redhat.com>
------- Additional Comments From mhiramat at redhat dot com 2008-10-01 20:56 -------
(In reply to comment #3)
> I would prefer to keep c->busy, since it also functions as a
> reentrancy-prevention mechanism, not just a shutdown-synchronization
> one.
Oops, Indeed.
BTW, kprobes itself has reentrancy checking routine, however other
probes(markers/timer/etc.) don't have that(and also don't exclude each other).
So it should be suspended until solving reentrant-probing support...
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |SUSPENDED
http://sourceware.org/bugzilla/show_bug.cgi?id=6932
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-10-01 20:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 20:39 [Bug translator/6932] New: use synchronize_sched() instead of c->busy checking mhiramat at redhat dot com
2008-10-01 20:44 ` [Bug translator/6932] " fche at redhat dot com
2008-10-01 20:49 ` [Bug translator/6932] c->busy can be removed from kprobe-based handlers mhiramat at redhat dot com
2008-10-01 20:51 ` fche at redhat dot com
2008-10-01 20:57 ` mhiramat at redhat dot com [this message]
2008-11-13 0:48 ` [Bug translator/6932] c->busy can be non-atomic mhiramat at redhat dot com
2008-11-13 0:48 ` [Bug translator/6932] c->busy can be removed from kprobe-based handlers mhiramat at redhat dot com
2008-11-13 14:40 ` [Bug translator/6932] c->busy can be non-atomic fche at redhat dot com
2008-11-13 16:06 ` mhiramat at redhat dot com
2008-11-13 17:38 ` mhiramat at redhat dot com
2009-02-27 22:16 ` mhiramat at redhat dot com
2009-02-28 0:58 ` jistone at redhat dot com
2009-02-28 2:04 ` mhiramat at redhat dot com
2009-02-28 2:22 ` mhiramat at redhat dot com
2009-02-28 14:27 ` jistone at redhat dot com
2009-02-28 20:43 ` fche at redhat dot com
2009-03-02 14:56 ` jistone at redhat dot com
2009-03-03 9:53 ` fche at redhat dot com
2009-03-03 16:01 ` mhiramat at redhat dot com
2009-03-03 21:44 ` jistone at redhat dot com
2009-03-03 22:24 ` jistone at redhat dot com
2009-03-08 0:00 ` jistone at redhat dot com
2009-03-08 0:33 ` fche at redhat dot com
2009-03-09 10:03 ` jistone at redhat dot com
2009-03-09 11:01 ` 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=20081001205641.10464.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).