Bug 1450336

Summary:	[NegativeLookup] Samba crash when continuous mount and unmount is done along with negative look up
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vivek Das <vdas>
Component:	samba	Assignee:	Poornima G <pgurusid>
Status:	CLOSED ERRATA	QA Contact:	Vivek Das <vdas>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	amukherj, ndevos, pgurusid, rhinduja, rhs-smb, rkavunga
Target Milestone:	---
Target Release:	RHGS 3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8.4-26	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-21 04:41:45 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:	1417151

Description Vivek Das 2017-05-12 09:46:31 UTC

Description of problem:
Samba crash when a continuous mount and unmount is done along with negative look up over a file

Version-Release number of selected component (if applicable):
glusterfs-server-3.8.4-24.el7rhgs.x86_64
samba-4.6.3-0.el7rhgs.x86_64

How reproducible:
1/1

Steps to Reproduce:
1. Run a script that mounts and unmounts a volume share on loop in windows client
2. ll for a file which is not present in the directory


Actual results:
Samba crashed

Expected results:
Samba should not crash

Additional info:

Comment 2 Poornima G 2017-05-12 12:38:24 UTC

Patches posted upstream : https://review.gluster.org/#/c/17068/  and https://review.gluster.org/#/c/17143/

Comment 9 Vivek Das 2017-06-08 10:30:11 UTC

Followed the steps to reproduced and also worked the same from multiple clients at a time, no crash was seen.

Version
---------
samba-client-4.6.3-2.el7rhgs.x86_64
glusterfs-3.8.4-27.el7rhgs.x86_64


Hence marking this as verified.

Comment 11 errata-xmlrpc 2017-09-21 04:41:45 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2774