Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionIchiko Sakamoto
2017-12-20 07:53:56 UTC
Description of problem:
staprun(8) manual says
"Users can also detach from the kernel module interactively by sending the SIGQUIT signal from the keyboard".
But, staprun cannot detach from kernel module with SIGQUIT.
Version-Release number of selected component (if applicable):
systemtap-runtime-3.1-4.el7_4.x86_64
How reproducible:
Always.
Steps to Reproduce:
1. Load module
# staprun -L xxx.ko
2. Attach
# staprun xxx
3. Send SIGQUIT
Actual results:
The kernel module was unloaded and staprun exited.
Expected results:
staprun detached from the kernel module and exited.
Additional info:
stp_main_loop seems to ignore "load_only" flag when receiving STP_EXIT.
mainloop.c
--
599 int stp_main_loop(void)
...
819 case STP_EXIT:
820 {
821 /* module asks us to unload it and exit */
822 dbug(2, "got STP_EXIT\n");
823 if (monitor)
824 monitor_exited();
825 else
826 cleanup_and_exit(0, error_detected);
^ detach = 0
827 /* monitor mode exit handled elsewhere, later. */
828 break;
829 }
--
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, 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/RHEA-2018:0906
Description of problem: staprun(8) manual says "Users can also detach from the kernel module interactively by sending the SIGQUIT signal from the keyboard". But, staprun cannot detach from kernel module with SIGQUIT. Version-Release number of selected component (if applicable): systemtap-runtime-3.1-4.el7_4.x86_64 How reproducible: Always. Steps to Reproduce: 1. Load module # staprun -L xxx.ko 2. Attach # staprun xxx 3. Send SIGQUIT Actual results: The kernel module was unloaded and staprun exited. Expected results: staprun detached from the kernel module and exited. Additional info: stp_main_loop seems to ignore "load_only" flag when receiving STP_EXIT. mainloop.c -- 599 int stp_main_loop(void) ... 819 case STP_EXIT: 820 { 821 /* module asks us to unload it and exit */ 822 dbug(2, "got STP_EXIT\n"); 823 if (monitor) 824 monitor_exited(); 825 else 826 cleanup_and_exit(0, error_detected); ^ detach = 0 827 /* monitor mode exit handled elsewhere, later. */ 828 break; 829 } --