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.
Cause:
Corosync receives sigabrt or sigsegv signal or user executes corosync -f
Consequence:
Files in /dev/shm created by corosync are not deleted resulting in lost of space in /dev/shm (-> memory)
Fix:
Properly register signal handlers and make sure to call cleanup function when processing -v parameter.
Result:
No files left in /dev/shm.
Description of problem:
When corosync receives sigabrt or sigsegv it doesn't delete libqb blackbox file (/dev/shm one). Same happens when corosync is executed with -v parameter (this shows only version, so it shouldn't cause leak in /dev/shm).
Version-Release number of selected component (if applicable):
7.0
How reproducible:
100%
Steps to Reproduce 1:
1. Start corosync
2. Send sigabrt to corosync
Steps to Reproduce 1:
1. Execute corosync -v
Actual results:
File like qb-corosync-*-blackbox-data|header exists results in leak of /dev/shm space.
Expected results:
No leak
Additional info:
Created attachment 916863[details]
fix memory leak produced by 'corosync -v'
fix memory leak produced by 'corosync -v'
Signed-off-by: zouyu <hopkings2005>
Reviewed-by: Jan Friesse <jfriesse>
Created attachment 916864[details]
Handle SIGSEGV and SIGABRT signals
Handle SIGSEGV and SIGABRT signals
SIGSEGV and SIGABRT signals are now correctly handled (blackbox is
dumped and logsys is finalized).
Signed-off-by: zouyu <hopkings2005>
Reviewed-by: Jan Friesse <jfriesse>
Created attachment 916865[details]
Fix compiler warning introduced by previous patch
Fix compiler warning introduced by previous patch
QB loop signal handler prototype differs from signal(2) prototype.
Solution is to create wrapper functions.
Signed-off-by: Jan Friesse <jfriesse>
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://rhn.redhat.com/errata/RHBA-2015-0365.html