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.
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.