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: Tue, 12 Mar 2024 16:13:04 +0000	[thread overview]
Message-ID: <bug-31472-6586-dObjxYKkzp@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|NEW                         |ASSIGNED

--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
The following message appears to be saying it is attempting to put in a jump
patch on the tracepoint module which is very odd (it should be trying to
instrument itself):

[ 6315.911726] jump_label: Fatal kernel bug, unexpected op at
__access_process_vm_.constprop.0+0x3d/0x1f0 [tracepoints] [0000000071a5b3f1]
(e9 eb 00 00 00 != 0f 1f 44 00 00)) size:5 type:1

The kernel checks to determine whether the location is a valid location for a
jump patch if it doesn't match the expected form the following line prints out
the message followed by a BUG() which cause the reboot:

https://elixir.bootlin.com/linux/v5.14/source/arch/x86/kernel/jump_label.c#L71

There seems to be something that is triggering this due to the number of
tracepoints being instrumented.  The RHEL 427 kernel only list out 21
tracepoints which the 428 kernel that has a problem with the tracepoints.stp
test has 2173 tracepoints listed.  Playing around with the list of tracepoints
in all_tracepoint to see see if can get a smaller set tracepoints that trigger
the reboot.

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

  parent reply	other threads:[~2024-03-12 16:13 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 [this message]
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

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-dObjxYKkzp@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).