public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dinghui at sangfor dot com.cn" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/26957] New: kernel crash when staprun ko which build id not matched
Date: Fri, 27 Nov 2020 03:51:27 +0000	[thread overview]
Message-ID: <bug-26957-6586@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26957
           Summary: kernel crash when staprun ko which build id not
                    matched
           Product: systemtap
           Version: unspecified
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: runtime
          Assignee: systemtap at sourceware dot org
          Reporter: dinghui at sangfor dot com.cn
  Target Milestone: ---

When we build a ko by stap, which 

diff --git a/runtime/sym.c b/runtime/sym.c
index a51f08c9e..521aebe48 100644
--- a/runtime/sym.c
+++ b/runtime/sym.c
@@ -735,7 +735,7 @@ static int _stp_build_id_check (struct _stp_module *m,
      // we make sure below is really a warning.
           _stp_warn ("Build-id mismatch [man warning::buildid]: \"%s\" pid %ld
address "
             "%#lx, expected %s actual %s\n",
-                     m->path, (long) tsk->tgid,
+                     m->path, (long) (tsk ? tsk->tgid : 0),
                      notes_addr, hexstring_theory, hexstring_practice);
       return 1;
   }

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

             reply	other threads:[~2020-11-27  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27  3:51 dinghui at sangfor dot com.cn [this message]
2020-11-27  4:14 ` [Bug runtime/26957] " dinghui at sangfor dot com.cn

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-26957-6586@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).