Bug 1804656

Summary: gfapi: tcmu-runner receives SEGV on calling glfs_init() after glfs_fini()
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prasanna Kumar Kalever <prasanna.kalever>
Component: gluster-blockAssignee: Prasanna Kumar Kalever <prasanna.kalever>
Status: CLOSED ERRATA QA Contact: Arun Kumar <arukumar>
Severity: high Docs Contact:
Priority: unspecified    
Version: ocs-3.11CC: arukumar, asriram, hchiramm, jahernan, jmulligan, jthottan, madam, moagrawa, pasik, pkarampu, pprakash, prasanna.kalever, puebele, rcyriac, rgeorge, rhs-bugs, rtalur, sabose, sheggodu, skoduri, storage-qa-internal, susgupta, vamahaja, vbellur, xiubli
Target Milestone: ---Keywords: ZStream
Target Release: OCS 3.11.z Async   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
Story Points: ---
Clone Of: 1796628 Environment:
Last Closed: 2020-03-10 14:40:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1800703    
Bug Blocks: 1796628    

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