From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/17461] probing process.end crashes on busy systems
Date: Mon, 06 Oct 2014 21:12:00 -0000 [thread overview]
Message-ID: <bug-17461-6586-OixtQMBS9k@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17461-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17461
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dsmith at redhat dot com
--- Comment #3 from David Smith <dsmith at redhat dot com> ---
I'd certainly suspect utrace, especially since I see utrace_free() in your
dmesg output. However, I also see _raw_spin_lock, and that's got me confused.
We added some patches recently to add support for realtime kernels, but we
shouldn't be using raw spinlocks anywhere but realtime kernels.
The only real utrace change lately was the following:
====
commit d9d07e99777c6e7aaaa8db0049c5fd5e5a2f01b0
Author: David Smith <dsmith@redhat.com>
Date: Fri Jul 18 15:49:39 2014 -0500
Fixed PR17181 by making utrace handle interrupting processes better.
====
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-10-06 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 20:49 [Bug runtime/17461] New: " jlebon at redhat dot com
2014-10-06 20:50 ` [Bug runtime/17461] " jlebon at redhat dot com
2014-10-06 20:52 ` jlebon at redhat dot com
2014-10-06 21:12 ` dsmith at redhat dot com [this message]
2015-05-13 20:31 ` jlebon at redhat dot com
2021-05-04 1:06 ` 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=bug-17461-6586-OixtQMBS9k@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).