[Bug kprobes/26755] New: recent rawhide: grabbing several lock:lock_* tracepoints leads to hard lockup?

me at serhei dot io sourceware-bugzilla@sourceware.org
Mon Oct 19 19:54:46 GMT 2020


https://sourceware.org/bugzilla/show_bug.cgi?id=26755

            Bug ID: 26755
           Summary: recent rawhide: grabbing several lock:lock_*
                    tracepoints leads to hard lockup?
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: kprobes
          Assignee: systemtap at sourceware dot org
          Reporter: me at serhei dot io
  Target Milestone: ---

Started seeing this on the rawhide buildbot with kprobes_onthefly.exp (which
probes all possible tracepoints in the 'hardcore' case). On a lockdep enabled
kernel this grabs lock:lock_{acquire,acquired,release,contended}.

The tricky part is that the hard lockup only happens if more than one of these
tracepoints is probed.

For now I'm disabling those tracepoints in the testcase (similar to hcall_*
blacklist on ppc) but we need to figure out if something/anything needs to be
blacklisted for recent kernels.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Systemtap mailing list