Bug 1435943

Summary:	When parallel readdir is enabled and there are simultaneous readdir and disconnects, then it results in crash
Product:	[Community] GlusterFS	Reporter:	Poornima G <pgurusid>
Component:	read-ahead	Assignee:	Poornima G <pgurusid>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, nbalacha
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.11.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1435946 (view as bug list)		Environment:
Last Closed:	2017-05-30 18:48:21 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:	1435946

Description Poornima G 2017-03-26 02:37:32 UTC

Description of problem:
Test case ./tests/bugs/bug-1110262.t fails on enabling parallel readdir

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


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2017-03-26 02:38:25 UTC

REVIEW: https://review.gluster.org/16948 (protocol-client: Initialize the list_head before using) posted (#1) for review on master by Poornima G (pgurusid)

Comment 2 Worker Ant 2017-03-27 00:56:23 UTC

COMMIT: https://review.gluster.org/16948 committed in master by Raghavendra G (rgowdapp) 
------
commit 98f602cd64e3f8cc7e4c4a7245e132c0afd7347f
Author: Poornima G <pgurusid>
Date:   Sun Mar 26 07:59:53 2017 +0530

    protocol-client: Initialize the list_head before using
    
    In client3_3_readdir(p)_cbk, in case of error conditions,
    it is possible that the list_head is used before initializing.
    Hence move the initialization before usage.
    
    Change-Id: Ie58902d079fdc58416d17b5fa5f61375decb1c99
    BUG: 1435943
    Signed-off-by: Poornima G <pgurusid>
    Reviewed-on: https://review.gluster.org/16948
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Raghavendra G <rgowdapp>

Comment 3 Shyamsundar 2017-05-30 18:48:21 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.11.0, please open a new bug report.

glusterfs-3.11.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-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/