Bug 1449236

Summary:	Fix the name of inode_t 's ref to refcount
Product:	[Community] GlusterFS	Reporter:	Sonal <sarora>
Component:	core	Assignee:	Sonal <sarora>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.1.3 (or later)	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-29 03:34:57 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 Sonal 2017-05-09 13:14:04 UTC

Description of problem:
I am creating a script using system tap tool to detect ref leaks in gluster. So while probing ref count in referencing/dereferencing functions (dict_ref, dict_unref, inode_ref, inode_unref, fd_ref, fd_unref), name of the variable which keeps ref count is different in different structures (in inode_t it was ref, elsewhere it is refcount). So this thing was making the script less dynamic. So i fixed the name of the attribute (to refcount) to make it common for all structures. 



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

How reproducible:
Check the inode_t structure's attribute ref.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Worker Ant 2017-05-09 14:09:03 UTC

REVIEW: https://review.gluster.org/17220 (libglusterfs/src/ : fix inode_t's ref attribute to refcount) posted (#1) for review on master by Sonal Arora (sarora)

Comment 2 Worker Ant 2017-05-15 13:39:28 UTC

REVIEW: https://review.gluster.org/17220 (libglusterfs/src/ : fix inode_t's ref attribute to refcount) posted (#2) for review on master by Sonal Arora (sarora)

Comment 3 Amar Tumballi 2018-08-29 03:34:57 UTC

This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.