From: "agentzh at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31907] New: STP_TIMING: BUG: using smp_processor_id() in preemptible on debug kernels
Date: Tue, 18 Jun 2024 23:09:44 +0000 [thread overview]
Message-ID: <bug-31907-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31907
Bug ID: 31907
Summary: STP_TIMING: BUG: using smp_processor_id() in
preemptible on debug kernels
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: agentzh at gmail dot com
Target Milestone: ---
We've noted that while running systemtap with STP_TIMING and debug kernels, we
would see kernel error messages like this:
```
[ 4565.662398] BUG: using smp_processor_id() in preemptible [00000000]
code: stapio/1158102
[ 4565.662416] caller is _stp_stat_add+0x4c/0x6f3 [stap_timing_t1]
[ 4565.662485] CPU: 10 PID: 1158102 Comm: stapio Kdump: loaded Tainted: GF
W OE ------- --- 5.14.0-362.8.1.el9_3.x86_64+debug #1
[ 4565.662494] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS
1.15.0-1 04/01/2014
[ 4565.662508] Call Trace:
[ 4565.662512] <TASK>
[ 4565.662521] dump_stack_lvl+0x57/0x81
[ 4565.662544] check_preemption_disabled+0xdd/0xe0
[ 4565.662556] _stp_stat_add+0x4c/0x6f3 [stap_timing_t1]
[ 4565.662594] systemtap_module_init+0x3cf/0x480 [stap_timing_t1]
[ 4565.662634] _stp_handle_start+0xf8/0x310 [stap_timing_t1]
[ 4565.662670] _stp_ctl_write_cmd+0x309/0x410 [stap_timing_t1]
```
Will prepare a patch to fix this.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-06-18 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 23:09 agentzh at gmail dot com [this message]
2024-06-18 23:32 ` [Bug runtime/31907] " agentzh at gmail 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-31907-6586@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).