Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1158903 - [linearstore] segfault when 2 journals request new journal file from empty EFP
[linearstore] segfault when 2 journals request new journal file from empty EFP
Status: CLOSED ERRATA
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
3.0
All Linux
high Severity high
: 3.2
: ---
Assigned To: Kim van der Riet
Michal Toth
: Patch
Depends On: 1150397
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-30 09:31 EDT by Mike Cressman
Modified: 2015-10-08 09:09 EDT (History)
10 users (show)

See Also:
Fixed In Version: qpid-cpp-0.30-4
Doc Type: Bug Fix
Doc Text:
It was discovered that when two journals concurrently requested a new journal file from an empty EFP, the Broker could segfault. A fix to popEmptyFile now performs an _atomic_ test-and-create-and-grab for the EFP file, which prevents the segfault from occurring.
Story Points: ---
Clone Of: 1150397
Environment:
Last Closed: 2015-10-08 09:09:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
qpidd kill segfault (3.97 KB, text/plain)
2015-08-12 08:32 EDT, Michal Toth
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Apache JIRA QPID-6157 None None None Never
Red Hat Product Errata RHEA-2015:1879 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 3.2 Release 2015-10-08 13:07:53 EDT

  None (edit)
Comment 23 Michal Toth 2015-08-12 08:32:32 EDT
Created attachment 1061932 [details]
qpidd kill segfault
Comment 25 Michal Toth 2015-08-19 04:17:20 EDT
Marking this bug as verified for supported platforms using 
qpid-cpp-server-0.34-1
qpid-cpp-server-linearstore-0.34-1

Thank you for your help Kim.
Comment 27 errata-xmlrpc 2015-10-08 09:09:49 EDT
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/RHEA-2015-1879.html

Note You need to log in before you can comment on or make changes to this bug.