Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1217949

Summary:	Null check before freeing dir_dfmeta and tmp_container
Product:	[Community] GlusterFS	Reporter:	Susant Kumar Palai <spalai>
Component:	distribute	Assignee:	Susant Kumar Palai <spalai>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, nbalacha, nsathyan
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-16 12:57:38 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 Susant Kumar Palai 2015-05-03 09:04:08 UTC

Description of problem:
 When local_subvol_cnt is zero in gf_defrag_process_dir, it goes to out section and tries to free dfmeta members which leads to crash as dfmeta is NULL.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Rebalance crashes

Expected results:


Additional info:

Comment 1 Anand Avati 2015-05-03 09:29:59 UTC

REVIEW: http://review.gluster.org/10459 (dht: Add a null check before freeing dir_dfmeta and tmp_container) posted (#4) for review on master by Susant Palai (spalai)

Comment 2 Anand Avati 2015-05-05 17:50:17 UTC

REVIEW: http://review.gluster.org/10281 (cluster/dht: change log level of developer logs to DEBUG) posted (#2) for review on master by Vijay Bellur (vbellur)

Comment 3 Nithya Balachandran 2015-05-08 10:36:48 UTC

http://review.gluster.org/#/c/10459/ is merged in master.

Comment 4 Anand Avati 2015-05-09 07:15:02 UTC

COMMIT: http://review.gluster.org/10281 committed in master by Vijay Bellur (vbellur) 
------
commit 8812e4f57f2138c159d99432748cf68240241675
Author: Vijay Bellur <vbellur>
Date:   Fri Apr 17 12:00:48 2015 +0530

    cluster/dht: change log level of developer logs to DEBUG
    
    A few log messages in dht directory self heal at log level INFO are useful
    only for developers and these logs tend to casue excessive logs in our
    log files. Hence moving the log level of such logs to DEBUG.
    
    Change-Id: I8a543f4ddeb5c20b2978a0f7b18d8baccc935a54
    BUG: 1217949
    Signed-off-by: Vijay Bellur <vbellur>
    Reviewed-on: http://review.gluster.org/10281
    Reviewed-by: N Balachandran <nbalacha>
    Tested-by: Gluster Build System <jenkins.com>

Comment 5 Niels de Vos 2015-05-14 17:29:34 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:35:58 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 7 Niels de Vos 2015-05-14 17:38:19 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 8 Niels de Vos 2015-05-14 17:47:00 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.7.0, please open a new bug report.

glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 9 Niels de Vos 2016-06-16 12:57:38 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.8.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user