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/30777] Systemtap modules unable to run on systemtap supporting Intel CET IBT
Date: Tue, 22 Aug 2023 15:26:59 +0000	[thread overview]
Message-ID: <bug-30777-6586-0jGGFXwnKx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30777-6586@http.sourceware.org/bugzilla/>

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

--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
Created attachment 15077
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15077&action=edit
A sample module demonstrating a workaround approach

The flippy_ibt is a really basic module that has surrounds the indirect call
with a ibt_save and ibt_restore operation.  To test out on a machine that
support IBT:

tar xvf flippy_ibt.tar.gz
cd flippy_ibt
make -C /usr/src/kernels/$(uname -r) M=$PWD V=2 
sudo insmod flippy_ibt.ko
sudo rmmod flippy_ibt

You should see success (no trap for the missing ENDBR) in output of:

dmesg 

One can check that the kernel IBT support is actually active with the same
module by installing with:

sudo insmod flippy_ibt.ko ibt_disable=0

You will see a message on the terminal about a segmentation fault and there
will be a trap  for the missing ENDBR in the output of dmesg.

That

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

  parent reply	other threads:[~2023-08-22 15:27 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 [this message]
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

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-0jGGFXwnKx@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).