Description of problem: Current code is not checking whether the pool pointer is null or not Version-Release number of selected component (if applicable):NA How reproducible: NA Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/18407 (core: Verify pool pointer before destroying it) posted (#1) for review on master by Akarsha Rai (akrai)
REVIEW: https://review.gluster.org/18407 (core: Verify pool pointer before destroying it) posted (#2) for review on master by Akarsha Rai (akrai)
COMMIT: https://review.gluster.org/18407 committed in master by Jeff Darcy (jeff.us) ------ commit 9af20af096a14c6297ca8f89697f2a9e4e83bd8f Author: Akarsha Rai <akrai> Date: Thu Sep 28 07:18:56 2017 -0400 core: Verify pool pointer before destroying it Problem: Current code is not checking whether the pool pointer is null or not. Solution: Updated the code to verify pool pointer. Bug: 1496675 Change-Id: Ie1f2de4e4204fde15d2b1e3a966ea4c9e7b41534 Signed-off-by: Akarsha Rai <akrai>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report. glusterfs-3.13.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/