Bug 1709262

Summary:	Use GF_ATOMIC ops to update inode->nlookup
Product:	[Community] GlusterFS	Reporter:	baul <roidinev>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	experimental	CC:	atumball, bugs, moagrawa
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1644164	Environment:
Last Closed:	2019-05-18 06:38:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description baul 2019-05-13 09:47:57 UTC

+++ This bug was initially created as a clone of Bug #1644164 +++

Description of problem:
Use GF_ATOMIC ops to update inode->nlookup

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


How reproducible:
It is just an enhancement to use atomic ops to update lookup counter.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2018-10-30 07:09:56 UTC ---

REVIEW: https://review.gluster.org/21305 (core: Use GF_ATOMIC ops to update inode->nlookup) posted (#3) for review on master by MOHIT AGRAWAL

--- Additional comment from Worker Ant on 2018-10-30 11:40:54 UTC ---

REVIEW: https://review.gluster.org/21305 (core: Use GF_ATOMIC ops to update inode->nlookup) posted (#3) for review on master by MOHIT AGRAWAL

--- Additional comment from Shyamsundar on 2019-03-25 16:31:39 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-6.0, please open a new bug report.

glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/

--- Additional comment from Worker Ant on 2019-05-13 09:26:50 UTC ---

REVIEW: https://review.gluster.org/22715 (core: Use GF_ATOMIC ops to update inode->nlookup) posted (#2) for review on release-3.12 by None

Comment 1 baul 2019-05-13 09:48:59 UTC

fix in 3.12 release

Comment 2 Worker Ant 2019-05-13 09:50:54 UTC

REVIEW: https://review.gluster.org/22715 (core: Use GF_ATOMIC ops to update inode->nlookup) posted (#4) for review on release-3.12 by None

Comment 3 Amar Tumballi 2019-05-18 06:38:22 UTC

Considering the request was for 3.12 branch, which is not maintained anymore, closing it as WONTFIX.