RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1902696 - regression running staprun under a stapusrer ID (rhel-8.3 vs. rhel-8.4)
Summary: regression running staprun under a stapusrer ID (rhel-8.3 vs. rhel-8.4)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemtap
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Frank Ch. Eigler
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-30 12:50 UTC by Martin Cermak
Modified: 2021-09-17 14:55 UTC (History)
5 users (show)

Fixed In Version: systemtap-4.4-8.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1908904 (view as bug list)
Environment:
Last Closed: 2021-05-18 15:44:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Martin Cermak 2020-11-30 12:50:29 UTC 
Upstream commit 7615cae790c899bc8a82841c75c8ea9c6fa54df3 broke staprun's ability to insert a module under a stapusr ID:


----> su stapusrer -c 'staprun -vvvvv /lib/modules/4.18.0-240.1.1.el8_3.x86_64/systemtap/dummy.ko'
staprun:parse_modpath:430 inpath=/lib/modules/4.18.0-240.1.1.el8_3.x86_64/systemtap/dummy.ko
staprun:main:485 modpath="/lib/modules/4.18.0-240.1.1.el8_3.x86_64/systemtap/dummy.ko", modname="dummy"
staprun:init_staprun:391 init_staprun
staprun:insert_module:71 inserting module /lib/modules/4.18.0-240.1.1.el8_3.x86_64/systemtap/dummy.ko
staprun:insert_module:97 module options: _stp_bufsize=0
staprun:insert_module:105 module path canonicalized to '/usr/lib/modules/4.18.0-240.1.1.el8_3.x86_64/systemtap/dummy.ko'
staprun:check_signature:427 checking signature for /usr/lib/modules/4.18.0-240.1.1.el8_3.x86_64/systemtap/dummy.ko
Signature file /usr/lib/modules/4.18.0-240.1.1.el8_3.x86_64/systemtap/dummy.ko.sgn not found
staprun:check_signature:440 verify_module returns 0
staprun:insert_module:191 Module dummy inserted from file /usr/lib/modules/4.18.0-240.1.1.el8_3.x86_64/systemtap/dummy.ko
ERROR: Couldn't insert module '/lib/modules/4.18.0-240.1.1.el8_3.x86_64/systemtap/dummy.ko': File exists
ERROR: Rerun with staprun option '-R' to rename this module.
----> 


There is one old and stable qe test covering this.  It now fails on line 93 here:

http://pkgs.devel.redhat.com/cgit/tests/systemtap/tree/Security/CVE-2011-2502-staprun-able-to-load-arbirary-module-OF/runtest.sh#n93

Rollong back commit 7615cae790c899bc8a82841c75c8ea9c6fa54df3 does fix the issue.
Comment 1 Martin Cermak 2020-11-30 14:27:56 UTC 
The problem seems to be in init_ctl_channel() :



# su stapusrer -c 'staprun  -vvvvv /lib/modules/4.18.0-254.el8.x86_64/systemtap/dummy.ko'
staprun:parse_modpath:430 inpath=/lib/modules/4.18.0-254.el8.x86_64/systemtap/dummy.ko
staprun:main:485 modpath="/lib/modules/4.18.0-254.el8.x86_64/systemtap/dummy.ko", modname="dummy"
staprun:init_staprun:391 init_staprun
staprun:insert_module:71 inserting module /lib/modules/4.18.0-254.el8.x86_64/systemtap/dummy.ko
staprun:insert_module:97 module options: _stp_bufsize=0
staprun:insert_module:105 module path canonicalized to '/usr/lib/modules/4.18.0-254.el8.x86_64/systemtap/dummy.ko'
staprun:check_signature:427 checking signature for /usr/lib/modules/4.18.0-254.el8.x86_64/systemtap/dummy.ko
Signature file /usr/lib/modules/4.18.0-254.el8.x86_64/systemtap/dummy.ko.sgn not found
staprun:check_signature:440 verify_module returns 0
staprun:insert_module:191 Module dummy inserted from file /usr/lib/modules/4.18.0-254.el8.x86_64/systemtap/dummy.ko
staprun:init_ctl_channel:92 Opened  (-1)
ERROR: Cannot attach to module dummy control channel; not running?
staprun:remove_module:246 dummy
staprun:init_ctl_channel:92 Opened  (-1)
ERROR: Cannot attach to module dummy control channel; not running?
ERROR: 'dummy' is not a zombie systemtap module.
#
Comment 2 Frank Ch. Eigler 2020-12-14 02:17:08 UTC 
fixed upstream
https://sourceware.org/bugzilla/show_bug.cgi?id=23512
Comment 3 Frank Ch. Eigler 2020-12-14 02:20:55 UTC 
correction,
https://sourceware.org/bugzilla/show_bug.cgi?id=27067
Comment 7 errata-xmlrpc 2021-05-18 15:44:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (systemtap bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1829
Note You need to log in before you can comment on or make changes to this bug.