From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: David Smith <dsmith@redhat.com>
Cc: Jim Keniston <jkenisto@linux.vnet.ibm.com>,
Josh Stone <jistone@redhat.com>,
Mark Wielaard <mjw@redhat.com>,
systemtap@sourceware.org
Subject: Re: Fixed PR13146 by not allowing memory allocations to sleep (Was: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-151-g8e794e9)
Date: Wed, 05 Oct 2011 16:00:00 -0000 [thread overview]
Message-ID: <20111005160018.GA27797@in.ibm.com> (raw)
In-Reply-To: <4E8C5FC3.6070007@redhat.com>
On Wed, Oct 05, 2011 at 08:46:43AM -0500, David Smith wrote:
> On 09/27/2011 06:00 PM, Jim Keniston wrote:
>
> > I haven't seen this explicitly mentioned wrt this thread or PR13146, but
> > uprobes and uretprobe handlers (which are called from the utrace
> > report_signal callback) can sleep.
>
>
> Jim,
>
> For my information, can uprobe/uretprobe handlers sleep in the new
> uprobes being proposed upstream?
Yes, they can sleep. The handlers get called on the path back to
userspace (do_notify_resume()) similar to what utrace used to do.
Ananth
next prev parent reply other threads:[~2011-10-05 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110901143940.13672.qmail@sourceware.org>
2011-09-27 14:52 ` Mark Wielaard
2011-09-27 22:03 ` Josh Stone
2011-09-27 23:01 ` Jim Keniston
2011-09-28 12:12 ` Mark Wielaard
2011-10-05 13:44 ` David Smith
2011-10-05 13:47 ` David Smith
2011-10-05 15:24 ` Jim Keniston
2011-10-05 16:00 ` Ananth N Mavinakayanahalli [this message]
2011-10-25 12:07 ` Fixed PR13146 by not allowing memory allocations to sleep Frank Ch. Eigler
2011-10-25 12:19 ` Mark Wielaard
2011-10-31 10:26 ` Mark Wielaard
2011-10-31 15:19 ` Frank Ch. Eigler
2011-10-31 15:30 ` Mark Wielaard
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=20111005160018.GA27797@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=dsmith@redhat.com \
--cc=jistone@redhat.com \
--cc=jkenisto@linux.vnet.ibm.com \
--cc=mjw@redhat.com \
--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).