From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/26307] New: kernel commit ed66f991bb19 breaks module initialization
Date: Tue, 28 Jul 2020 10:09:27 +0000 [thread overview]
Message-ID: <bug-26307-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26307
Bug ID: 26307
Summary: kernel commit ed66f991bb19 breaks module
initialization
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: fche at redhat dot com
Target Milestone: ---
staprun of any module after $subject commit causes a kernel BUG: (which
cleanishly terminates staprun rather than bringing down the system,
thankfully). Cause is change to the internal module_sect_attr machinery, which
logic in runtime/linux/symbols.c STAPCONF_MODULE_SECT_ATTRS needs to adapt to.
Alternately, rip this whole part out; access module section attributes via some
other in-kernel interface, or get staprun to send updates and incidentally lose
ability to probe module-init functions.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-07-28 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 10:09 fche at redhat dot com [this message]
2020-07-31 20:43 ` [Bug runtime/26307] " fche 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-26307-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).