This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug testsuite/23493] Test suite makes all CPU stuck forever on kernel 4.16.16 (Fedora 27)


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.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]