From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7BB5D3858D32; Fri, 22 Mar 2024 14:40:34 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7BB5D3858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1711118434; bh=uEnKkME/49hMyNOVMLfdLxIxPU4VpOiJrg9mqHfjTR8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=EcT5kqd+HrQCImcivt9mfj3rm+UtkGPXvPeubT9ytuOutnmOpSjlEa2u+cjO5gu/F /vVj599PUCf0qeyKcsKl9eXK43iyMxHBlrdWWQ+XUkrz0dwertGLE94NMPpnBpOFjv JXy9o066v8Gu5jabIUY+mwvQNi2CIHLgws1GFj8Q= From: "wcohen at redhat dot com" To: systemtap@sourceware.org Subject: [Bug runtime/31500] stapio exited with irqs disabled Date: Fri, 22 Mar 2024 14:40:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: runtime X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wcohen at redhat dot com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED 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_status resolution Message-ID: In-Reply-To: References: 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31500 William Cohen changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from William Cohen --- This issue should be addressed by the following patch: commit 7cc8f31116c5bf218572f88080f3009e5c474a0f (HEAD -> master, origin/mas= ter, origin/HEAD) Author: William Cohen Date: Fri Mar 22 10:29:49 2024 -0400 PR31500: Never allow probing of kernel __init or __kprobes functions When guru mode was used it was possble to get systemtap to instrument kernel functions marked with __init or __kprobes. By the time that systemtap instrumentation is being loaded a kernel __init marked functions has already run and may be in a section of memory that has been freed up. At best this probe will never trigger. At worst the registration of the probe will cause a memory fault causing the process to be killed. Also probes shouldn't be allowed on __kprobes functions as a rule. --=20 You are receiving this mail because: You are the assignee for the bug.=