Bug 1804656 - gfapi: tcmu-runner receives SEGV on calling glfs_init() after glfs_fini()
Summary: gfapi: tcmu-runner receives SEGV on calling glfs_init() after glfs_fini()
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-block
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 3.11.z Async
Assignee: Prasanna Kumar Kalever
QA Contact: Arun Kumar
URL:
Whiteboard:
Depends On: 1800703
Blocks: 1796628
TreeView+ depends on / blocked
 
Reported: 2020-02-19 10:54 UTC by Prasanna Kumar Kalever
Modified: 2020-07-15 09:37 UTC (History)
25 users (show)

Fixed In Version: gluster-block-0.2.1-36.el7rhgs
Doc Type: Bug Fix
Doc Text:
With Red Hat OpenShift Container Storage 3.11 Update 5, if a create block volume operation followed with the delete block volume operation on a given block hosting volume caused tcmu-runner service to crash with SEGV. This is caused due to memory corruption in glusterfs when global memory structures were destroyed and reinitialized as part of glfs_init() and glfs_fini(). As tcmu-runner uses gfapi library, it is the one that will receive SEGV signal. Now, with this update, memory pool management races were fixed in the core glusterfs, hence hereon no crashes will be observed by tcmu-runner or gluster-block daemons.
Clone Of: 1796628
Environment:
Last Closed: 2020-03-10 14:40:29 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0777 0 None None None 2020-03-10 14:40:39 UTC

Comment 18 errata-xmlrpc 2020-03-10 14:40:29 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.

https://access.redhat.com/errata/RHBA-2020:0777
Note You need to log in before you can comment on or make changes to this bug.