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

Bug 1330892

Summary:	nfs-ganesha crashes with segfault error while doing refresh config on volume.
Product:	[Community] GlusterFS	Reporter:	Soumya Koduri <skoduri>
Component:	ganesha-nfs	Assignee:	Soumya Koduri <skoduri>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.7.11	CC:	bugs, jthottan, kkeithle, ndevos, nlevinki, skoduri, sraj, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.12	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1326627	Environment:
Last Closed:	2016-06-28 12:15:37 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:	1325975, 1326627

Comment 1 Vijay Bellur 2016-04-27 09:12:29 UTC

REVIEW: http://review.gluster.org/14089 (inode: Always fetch first entry from the inode lists during inode_table_destroy) posted (#1) for review on release-3.7 by soumya k (skoduri)

Comment 2 Vijay Bellur 2016-04-28 06:06:13 UTC

REVIEW: http://review.gluster.org/14089 (inode: Always fetch first entry from the inode lists during inode_table_destroy) posted (#2) for review on release-3.7 by soumya k (skoduri)

Comment 3 Vijay Bellur 2016-04-28 10:40:12 UTC

REVIEW: http://review.gluster.org/14089 (inode: Always fetch first entry from the inode lists during inode_table_destroy) posted (#3) for review on release-3.7 by soumya k (skoduri)

Comment 4 Vijay Bellur 2016-04-29 09:06:27 UTC

COMMIT: http://review.gluster.org/14089 committed in release-3.7 by Kaleb KEITHLEY (kkeithle) 
------
commit c8e5d078ce8b02f1ce0a4692a1170cd760fbb260
Author: Soumya Koduri <skoduri>
Date:   Wed Apr 13 12:50:49 2016 +0530

    inode: Always fetch first entry from the inode lists during inode_table_destroy
    
    In inode_table_destroy, we iterate through lru and active lists
    to move the entries to purge list so that they can be destroyed
    during inode_table_prune.
    
    But if used "list_for_each_entry" or "list_for_each_entry_safe"
    to iterate, we could end up accessing the entries which may have
    got moved to different(purge) lists in the process and can result
    in either infinite loop or crash. The safe approach seems to fetch
    the first entry of the list in each iteration till it gets empty.
    
    This is backport of below mainline fix -
            http://review.gluster.org/13987
    
    Change-Id: I24a18881833bd9419c2d8e5e8807bc71ec396479
    BUG: 1330892
    Signed-off-by: Soumya Koduri <skoduri>
    Reviewed-on: http://review.gluster.org/13987
    Reviewed-by: Kaleb KEITHLEY <kkeithle>
    Reviewed-by: Niels de Vos <ndevos>
    Reviewed-by: Jeff Darcy <jdarcy>
    Reviewed-on: http://review.gluster.org/14089
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>

Comment 5 Kaushal 2016-06-28 12:15:37 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.12, please open a new bug report.

glusterfs-3.7.12 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] https://www.gluster.org/pipermail/gluster-devel/2016-June/049918.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user