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 869446 - Failure in ipc receive reply function can consume nearly 100% CPU resources
Summary: Failure in ipc receive reply function can consume nearly 100% CPU resources
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libqb
Version: 6.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: 6.4
Assignee: David Vossel
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-23 22:33 UTC by David Vossel
Modified: 2013-02-21 08:38 UTC (History)
3 users (show)

Fixed In Version: libqb-0.14.2-3.el6
Doc Type: Bug Fix
Doc Text:
Cause: Timeout argument give to qb_ipcc_recv() api function is not passed to poll() while waiting for reply. Consequence: Depending on how qb_ipcc_recv() is used, this issue has the potential to consume nearly 100% CPU resources. Pacemaker is affected by this use case. Fix: Pass timeout value to poll in qb_ipcc_recv(). Result: Timeout period is honored as expected and Pacemaker's use of ipc functions correctly.
Clone Of:
Environment:
Last Closed: 2013-02-21 08:38:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0323 0 normal SHIPPED_LIVE libqb bug fix and enhancement update 2013-02-20 20:54:45 UTC

Description David Vossel 2012-10-23 22:33:59 UTC 
Description of problem:

The ipc api function used to receive a reply (qb_ipcc_recv) does not honor the timeout period it takes in as an argument. Pacemaker depends on this timeout period to be used correctly.  There are situations in Pacemaker where incorrect behavior of qb_ipcc_recv causes Pacemaker to utilize nearly 100% cpu.

Version-Release number of selected component (if applicable):

libqb-0.14.2-1.el6

Additional info:

This issue originated on the upstream pacemaker bug tracker.
http://bugs.clusterlabs.org/show_bug.cgi?id=5110

A commit upstream to libqb has already been made to fix this.

https://github.com/asalkeld/libqb/commit/e771439
Comment 4 David Vossel 2012-11-19 21:02:18 UTC 
An additional commit made upstream is required to resolve this.

https://github.com/asalkeld/libqb/commit/709b32de434ec157ec2a73153e58ffec186ae660
Comment 9 errata-xmlrpc 2013-02-21 08:38:04 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, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHBA-2013-0323.html
Note You need to log in before you can comment on or make changes to this bug.