From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/13146] memory allocation can sleep
Date: Thu, 01 Sep 2011 14:51:00 -0000 [thread overview]
Message-ID: <bug-13146-6586-Oo0ZIEDf2A@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13146-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13146
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #1 from David Smith <dsmith at redhat dot com> 2011-09-01 14:50:44 UTC ---
Fixed in commit 8e794e9 (which also fixes a couple of places to handle memory
allocation failures better).
Regression tested on:
RHEL4: 2.6.9-100.ELsmp (i686)
RHEL5: 2.6.18-274.el5debug (x86_64)
RHEL6: 2.6.32-192.el6.x86_64.debug (x86_64)
f15: 2.6.40.3-0.fc15.i686.debug (i686)
rawhide: 3.0.1-6.fc17.x86_64 (x86_64)
Note that this came up while working on bug #10994. During some utrace probe
handlers, memory allocation is done (typically to allocate space for a
pathname). That is fine, since utrace probe handlers are run in a sleepable
context.
However, the new utrace-free task_finder will be implemented via tracepoints,
and tracepoint probe handers are not run in a sleepable context.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-09-01 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 14:35 [Bug runtime/13146] New: " dsmith at redhat dot com
2011-09-01 14:51 ` dsmith at redhat dot com [this message]
2011-09-01 14:52 ` [Bug runtime/13146] " dsmith 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-13146-6586-Oo0ZIEDf2A@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).