Bug 1369773

Summary:	Multiple fuse mount get the same client uuid
Product:	[Community] GlusterFS	Reporter:	Poornima G <pgurusid>
Component:	protocol	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	mainline	CC:	atumball, bugs, csaba, pgurusid
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 07:04:27 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 Poornima G 2016-08-24 11:42:30 UTC

Description of problem:
When there are consecutive fuse mounts done within lets say a span of 2 min, all of them get the same client uid, this could be dangerous with posix-locks, upcall and leases, which depends on client-uid for disconnect cleanup.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Amar Tumballi 2018-10-08 17:36:31 UTC

Is it still valid bug? Should we increase the priority?

Comment 2 Poornima G 2018-10-23 07:04:27 UTC

This is not valid anymore, it is fixed as a part of patch https://review.gluster.org/#/c/glusterfs/+/13901/

Closing the bug as fixed.