From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/30777] Systemtap modules unable to run on systemtap supporting Intel CET IBT
Date: Tue, 29 Aug 2023 15:53:24 +0000 [thread overview]
Message-ID: <bug-30777-6586-tpIYQSHVyF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30777-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30777
William Cohen <wcohen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from William Cohen <wcohen at redhat dot com> ---
The following commit has been added to the upstream systemtap git repo to
address the issue:
commit f70b8278cf39848c75a8bdcf4a41d7463422b666 (HEAD -> master, origin/master,
origin/HEAD)
Author: William Cohen <wcohen@redhat.com>
Date: Tue Aug 29 11:33:41 2023 -0400
PR30777: Allow systemtap to work on Intel machines with IBT enabled
Intel 11th gen processors include Indirect Branch Target (IBT)
support. Systemtap needs to take some additional steps to work in
this environment. For kernels that do not have CONFIG_X86_KERNEL_IBT
set these steps are turned into NOPS.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2023-08-29 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 15:37 [Bug runtime/30777] New: " wcohen at redhat dot com
2023-08-17 15:48 ` [Bug runtime/30777] " wcohen at redhat dot com
2023-08-22 15:26 ` wcohen at redhat dot com
2023-08-24 19:10 ` wcohen at redhat dot com
2023-08-27 23:40 ` wcohen at redhat dot com
2023-08-29 14:09 ` wcohen at redhat dot com
2023-08-29 15:53 ` 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-30777-6586-tpIYQSHVyF@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).