public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31074] On aarch64 the systemtap.base/set_kernel.stp triggers "Unable to handle kernel paging request"
Date: Wed, 22 Nov 2023 15:36:16 +0000	[thread overview]
Message-ID: <bug-31074-6586-o4AN4hURid@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31074-6586@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
... and as a temporary measure, could consider

diff --git a/runtime/linux/stp_tracepoint.c b/runtime/linux/stp_tracepoint.c
index 508948dce4fd..9b7409194956 100644
--- a/runtime/linux/stp_tracepoint.c
+++ b/runtime/linux/stp_tracepoint.c
@@ -286,7 +286,10 @@ int stp_tracepoint_coming(struct tp_module *tp_mod)
                #else
                tp = tp_mod->mod->tracepoints_ptrs[i];
                #endif
-               e = get_tracepoint(tp->name);
+                if (!tp) {
+                        WARN_ON(!tp);
+                        continue;
+                }
                if (!e) {
                        e = add_tracepoint(tp->name);
                        if (IS_ERR(e)) {

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

  parent reply	other threads:[~2023-11-22 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 17:13 [Bug runtime/31074] New: " wcohen at redhat dot com
2023-11-22  0:19 ` [Bug runtime/31074] " fche at redhat dot com
2023-11-22 15:02 ` wcohen at redhat dot com
2023-11-22 15:36 ` fche at redhat dot com [this message]
2023-11-27 16:07 ` wcohen at redhat dot com
2023-12-01 14:51 ` wcohen at redhat dot com
2023-12-01 16:45 ` wcohen at redhat dot com
2023-12-01 17:19 ` mark at klomp dot org
2023-12-04 16:38 ` wcohen 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-31074-6586-o4AN4hURid@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).