Bug 1510725

Summary: [GSS] glustersfd (brick) process crashed
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Prashant Dhange <pdhange>
Component: locksAssignee: Krutika Dhananjay <kdhananj>
Status: CLOSED ERRATA QA Contact: Nag Pavan Chilakam <nchilaka>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.2CC: amukherj, kdhananj, moagrawa, nchilaka, pdhange, pkarampu, rcyriac, rgowdapp, rhinduja, rhs-bugs, sheggodu, srmukher, vbellur
Target Milestone: ---   
Target Release: RHGS 3.4.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.12.2-1 Doc Type: Bug Fix
Doc Text:
When a stale lock on the volume is cleared using the gluster volume clear-locks <volname> command, one of the references to lock is still in memory even after the lock is destroyed. Upon disconnection from the client, this invalid memory is accessed which leads to a crash. With this fix, final reference to the lock is cleared as part of the clear-locks command, so the operation doesn't lead to unofficial memory access.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 06:39:09 UTC Type: Bug
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:    
Bug Blocks: 1503134, 1511256    

Comment 32 errata-xmlrpc 2018-09-04 06:39:09 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/RHSA-2018:2607