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: Mon, 18 Mar 2024 21:06:32 +0000 [thread overview]
Message-ID: <bug-31472-6586-NaTeQQiLMe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31472-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31472
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from William Cohen <wcohen at redhat dot com> ---
Fixed by:
commit deeee3e3667674a00fed6c42b8f028465271eab5
Author: William Cohen <wcohen@redhat.com>
Date: Thu Mar 14 15:27:17 2024 -0400
Revert "PR30716: Turn off objtool warnings on systemtap instrumentation
modules"
This reverts commit 155c689b2a75dcb217a1c52886c04982f4c169f2.
There are other things that objtool is doing in addition to checking
user accesses and disabling objtool with newer RHEL9
5.14.0-428.el9.x86_64 causes the system to reboot when setting up some
tracepoint probes (PR30472).
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2024-03-18 21:06 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
2024-03-18 21:06 ` wcohen at redhat dot com [this message]
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-NaTeQQiLMe@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).