Bug 1496675

Summary:	Verify pool pointer before destroying it
Product:	[Community] GlusterFS	Reporter:	akarsha <akrai>
Component:	core	Assignee:	akarsha <akrai>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	aspandey, bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.13.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-08 17:42:08 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:

Description akarsha 2017-09-28 06:03:08 UTC

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:

Comment 1 Worker Ant 2017-09-28 12:19:35 UTC

REVIEW: https://review.gluster.org/18407 (core: Verify pool pointer before destroying it) posted (#1) for review on master by Akarsha Rai (akrai)

Comment 2 Worker Ant 2017-09-28 12:40:59 UTC

REVIEW: https://review.gluster.org/18407 (core: Verify pool pointer before destroying it) posted (#2) for review on master by Akarsha Rai (akrai)

Comment 3 Worker Ant 2017-09-29 12:36:27 UTC

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>

Comment 4 Shyamsundar 2017-12-08 17:42:08 UTC

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/