Bug 601018 - logsys ring buffer needs to use file mapped backing properly as intended
logsys ring buffer needs to use file mapped backing properly as intended
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: corosync (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Steven Dake
Cluster QE
Depends On:
  Show dependency treegraph
Reported: 2010-06-06 22:16 EDT by Steven Dake
Modified: 2016-04-26 09:25 EDT (History)
1 user (show)

See Also:
Fixed In Version: corosync-1.2.3-2.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-15 08:53:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
upstream revision 2922 (3.76 KB, patch)
2010-06-15 13:33 EDT, Steven Dake
no flags Details | Diff

  None (edit)
Description Steven Dake 2010-06-06 22:16:13 EDT
Description of problem:
logsys buffer is not backed by shared memory segment, causing it to write off end of buffers and cause all other kinds of problems.

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

How reproducible:
hard to reproduce

Steps to Reproduce:
1.valgrind shows errors with some loads
Actual results:
valgrind errors

Expected results:
no valgrind errors regarding memory access

Additional info:
Comment 1 RHEL Product and Program Management 2010-06-06 22:33:27 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 2 Steven Dake 2010-06-15 13:33:08 EDT
Created attachment 424242 [details]
upstream revision 2922
Comment 4 releng-rhel@redhat.com 2010-11-15 08:53:43 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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