From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id ACF69388701C; Mon, 19 Oct 2020 19:54:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ACF69388701C From: "me at serhei dot io" To: systemtap@sourceware.org Subject: [Bug kprobes/26755] New: recent rawhide: grabbing several lock:lock_* tracepoints leads to hard lockup? Date: Mon, 19 Oct 2020 19:54:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: kprobes X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: me at serhei dot io X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: systemtap@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Systemtap mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2020 19:54:46 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D26755 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 enabl= ed kernel this grabs lock:lock_{acquire,acquired,release,contended}. The tricky part is that the hard lockup only happens if more than one of th= ese 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. --=20 You are receiving this mail because: You are the assignee for the bug.=