Bug 1449236 - Fix the name of inode_t 's ref to refcount
Summary: Fix the name of inode_t 's ref to refcount
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Sonal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-09 13:14 UTC by Sonal
Modified: 2018-08-29 03:34 UTC (History)
1 user (show)

Fixed In Version: glusterfs-4.1.3 (or later)
Clone Of:
Environment:
Last Closed: 2018-08-29 03:34:57 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.