public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31472] systemtap.base/tracepoints.stp causes reboot with RHEL9 linux 5.14.0-428.el9.x86_64
Date: Thu, 14 Mar 2024 18:51:44 +0000	[thread overview]
Message-ID: <bug-31472-6586-NJA5Dnq3IO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31472-6586@http.sourceware.org/bugzilla/>

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

--- Comment #5 from William Cohen <wcohen at redhat dot com> ---
Did a git bisect running against the RHEL9 428 kernel and verified that the
problem on RHEL9 is caused by:

commit 155c689b2a75dcb217a1c52886c04982f4c169f2
Author: William Cohen <wcohen@redhat.com>
Date:   Thu Mar 7 13:44:06 2024 -0500

    PR30716: Turn off objtool warnings on systemtap instrumentation modules

    The previous approaches to turning off the objtool warnings did not
    work for x86_64 RHEL9.  The systemtap generated code is not on the
    whitelist to use certain kernel functions. The additional objtool
    warning output mentioning the systemtap code using those functions
    with UACCESS enabled caused a number of the tests in the testsuite to
    fail.  The generated Makefile now includes a line to turn off running
    objtool on the systemtap generated module and eliminates those
    warnings.

There are additional sections on generated .ko module when objtool is run.  The
missing orc_unwind explains why the backtrace is looking a bit odd. Below shows
what sections the bad .ko is missing:

 diff -u0 a b
--- a   2024-03-13 15:26:23.637081062 -0400
+++ b   2024-03-13 15:25:58.343950133 -0400
@@ -7 +6,0 @@
-.call_sites
@@ -21,2 +19,0 @@
-.orc_unwind
-.orc_unwind_ip
@@ -27 +23,0 @@
-.rela.call_sites
@@ -32 +27,0 @@
-.rela.orc_unwind_ip
@@ -36,2 +30,0 @@
-.rela.retpoline_sites
-.rela.return_sites
@@ -40 +32,0 @@
-.rela.static_call_sites
@@ -43,2 +34,0 @@
-.retpoline_sites
-.return_sites
@@ -51 +40,0 @@
-.static_call_sites

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

  parent reply	other threads:[~2024-03-14 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 13:54 [Bug runtime/31472] New: " wcohen at redhat dot com
2024-03-11 13:57 ` [Bug runtime/31472] " fche at redhat dot com
2024-03-12 16:13 ` wcohen at redhat dot com
2024-03-12 18:16 ` wcohen at redhat dot com
2024-03-12 18:29 ` wcohen at redhat dot com
2024-03-14 18:51 ` wcohen at redhat dot com [this message]
2024-03-18 21:06 ` 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-31472-6586-NJA5Dnq3IO@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).