Bug 1369773 - Multiple fuse mount get the same client uuid
Summary: Multiple fuse mount get the same client uuid
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-24 11:42 UTC by Poornima G
Modified: 2018-10-23 07:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-10-23 07:04:27 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.