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

Bug 1533804

Summary:	readdir-ahead: change of cache-size should be atomic
Product:	[Community] GlusterFS	Reporter:	Zhang Huan <zhhuan>
Component:	unclassified	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, rgowdapp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-15 11:25:40 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 Zhang Huan 2018-01-12 09:37:12 UTC

Description of problem:
For readdir-ahead xlator, change of cache-size is not atomic. Need to convert its variable type to atomic to protect concurrent change of its value.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2018-01-12 09:53:21 UTC

REVIEW: https://review.gluster.org/19187 (performance/readdir-ahead: fix cache usage update issue) posted (#1) for review on master by Zhang Huan

Comment 2 Worker Ant 2018-01-15 05:08:53 UTC

COMMIT: https://review.gluster.org/19187 committed in master by \"Zhang Huan\" <zhanghuan> with a commit message- performance/readdir-ahead: fix cache usage update issue

Use atomic operation to modify cache-size to protect it from concurrent
modification.

Change-Id: Ie73cdd4abbaf0232b1db4ac856c01d24603890ad
BUG: 1533804
Signed-off-by: Zhang Huan <zhanghuan>

Comment 3 Shyamsundar 2018-03-15 11:25:40 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-4.0.0, please open a new bug report.

glusterfs-4.0.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/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/