Bug 1369703

Summary:	memory leak caused by client_uid
Product:	[Community] GlusterFS	Reporter:	Ryan Ding <ryan.ding>
Component:	locks	Assignee:	Susant Kumar Palai <spalai>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, pkarampu
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:35:21 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 Ryan Ding 2016-08-24 08:00:23 UTC

Description of problem:

features/locks xlator will leak memory after lock/unlock test.

Steps to Reproduce:

1. run lock/unlock test on fuse client (I use ltp's fs testcase, it include a lot file lock operation)
2. run for a while, use kill -s SIGUSR1 to see the memory usage. it will show like:

[features/locks.test_gfs-locks - usage-type gf_common_mt_strdup memusage]
size=66391322
num_allocs=1070830
max_size=66391322
max_num_allocs=1070830
total_allocs=1071338

a lot strdup memory have not been released.

Comment 1 Worker Ant 2016-08-24 08:16:17 UTC

REVIEW: http://review.gluster.org/15303 (features/locks: fix memory leak caused by client_uid) posted (#1) for review on master by Ryan Ding (ryan.ding)

Comment 2 Amar Tumballi 2018-08-29 03:35:21 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.