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/31500] stapio exited with irqs disabled
Date: Tue, 19 Mar 2024 15:49:01 +0000	[thread overview]
Message-ID: <bug-31500-6586-6cQvd7Ji1u@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31500-6586@http.sourceware.org/bugzilla/>

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

--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
The dmesg output is stating a page fault occurred.  CR2 holds the page-fault
linear address the access was attemtped on.  This was occurring in the
arch_adjust_kprobe_addr function.  On the x86_64 this function has to move
kprobes past the ENDBR instuction that is a target for a branch. If IBT
enabled, and the target of indirect branch is not an ENBR, it will be trapped
and killed.  The "Code:" section show what the code looks like.
The "<8b> 55 00" is the instruction which is a "mov 0x0(%rbp), %edx".  The
following dump of the registers show RBP has ffffffffa64a65c0, the same value
as CR2.  It looks like a bogus address is being used for a kprobe.  Are these
dmesgs showing up consistently around the same places in the "make
installcheck" runs (assuming not rebooting the system)?

It might be possible that the irq are disabled when the arch_adjust_kprobe_addr
function is running and when the stapio exits it makes a not of it
https://elixir.bootlin.com/linux/v6.8.1/source/kernel/exit.c#L944 .

stap_017c8012d60fc7fd31a84d27b5a28d_187649(OE)]
[16452.767193] CR2: ffffffffa64a65c0
[16452.769368] ---[ end trace 0000000000000000 ]---
[16452.771499] RIP: 0010:arch_adjust_kprobe_addr+0x41/0xe0
[16452.773611] Code: 48 89 d3 48 ba 00 00 00 00 00 fc ff df 48 83 ec 08 0f b6
0c 11 48 89 fa 83 e2 07 83 c2 03 38 ca 7c 08 84 c9 0f 85 85 00 00 00 <8b> 55 00
81 fa 66 0f 1f 00 74 4f 81 e2 ff ff ff fe b9 0c f0 e1 05
[16452.777850] RSP: 0018:ffffc90002027960 EFLAGS: 00010246
[16452.779941] RAX: 0000000000000001 RBX: ffffc90002027a58 RCX:
0000000000000000
[16452.782014] RDX: 0000000000000003 RSI: 0000000000000000 RDI:
ffffffffa64a65c0
[16452.784058] RBP: ffffffffa64a65c0 R08: fffffbfff4858cff R09:
0000000000000000
[16452.786089] R10: 0000000000000000 R11: 0000000000000001 R12:
1ffff92000404f31
[16452.788180] R13: ffffffffc10ca498 R14: 0000000000000000 R15:
ffffffffc20ada98
[16452.790166] FS:  00007f1eaa74a180(0000) GS:ffff888115400000(0000)
knlGS:0000000000000000
[16452.792138] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[16452.794077] CR2: ffffffffa64a65c0 CR3: 000000010e99e005 CR4:
0000000000370ef0
[16452.796007] DR0: 0000000000404010 DR1: 0000000000000000 DR2:
0000000000000000
[16452.797910] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000600
[16452.799774] note: stapio[188000] exited with irqs disabled

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

  parent reply	other threads:[~2024-03-19 15:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16 13:03 [Bug runtime/31500] New: " mcermak at redhat dot com
2024-03-18 21:48 ` [Bug runtime/31500] " wcohen at redhat dot com
2024-03-19  8:10 ` mcermak at redhat dot com
2024-03-19 15:49 ` wcohen at redhat dot com [this message]
2024-03-19 20:57 ` wcohen at redhat dot com
2024-03-20 14:19 ` wcohen at redhat dot com
2024-03-20 15:25 ` wcohen at redhat dot com
2024-03-20 21:10 ` wcohen at redhat dot com
2024-03-21 14:31 ` wcohen at redhat dot com
2024-03-21 15:13 ` wcohen at redhat dot com
2024-03-22 14:40 ` 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-31500-6586-6cQvd7Ji1u@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).