From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/23493] Test suite makes all CPU stuck forever on kernel 4.16.16 (Fedora 27)
Date: Wed, 29 Aug 2018 12:59:00 -0000 [thread overview]
Message-ID: <bug-23493-6586-fxn0N90iRD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23493-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23493
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #9 from Mark Wielaard <mark at klomp dot org> ---
(In reply to agentzh from comment #8)
> Is it a bug in the stap runtime or in the kernel?
It looks like this is caused by calling the kernel find_get_pid () function
from the pid2task tapset function when in kernel mode, just after the current
task died? I am not sure find_get_pid should/can be called from a kernel
context. It might assume the current pid actually exists? Maybe current is NULL
at this point and we should check for that first?
Do you have more context about which probe was hit when this happened?
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-08-29 12:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 17:23 [Bug testsuite/23493] New: Test suite makes all CPU stuck forever on kernel 2.6.16 " agentzh at gmail dot com
2018-08-07 17:23 ` [Bug testsuite/23493] Test suite makes all CPU stuck forever on kernel 2.16.16 " agentzh at gmail dot com
2018-08-07 17:24 ` [Bug testsuite/23493] Test suite makes all CPU stuck forever on kernel 4.16.16 " agentzh at gmail dot com
2018-08-07 17:26 ` agentzh at gmail dot com
2018-08-07 17:42 ` agentzh at gmail dot com
2018-08-08 23:03 ` fche at redhat dot com
2018-08-10 18:41 ` agentzh at gmail dot com
2018-08-10 18:43 ` agentzh at gmail dot com
2018-08-10 18:50 ` agentzh at gmail dot com
2018-08-26 6:27 ` agentzh at gmail dot com
2018-08-29 1:20 ` agentzh at gmail dot com
2018-08-29 12:59 ` mark at klomp dot org [this message]
2018-08-29 17:47 ` agentzh at gmail dot com
2018-08-29 18:02 ` agentzh at gmail dot com
2020-02-20 14:26 ` fche at redhat dot com
2020-02-20 20:41 ` agentzh at gmail dot com
2023-05-25 16:35 ` 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-23493-6586-fxn0N90iRD@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).