Bug 1702268

Summary:	Memory accounting information is not always accurate
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1702270 1702271 (view as bug list)		Environment:
Last Closed:	2019-04-23 11:55:51 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:
Bug Depends On:
Bug Blocks:	1702270, 1702271

Description Xavi Hernandez 2019-04-23 11:23:13 UTC

Description of problem:

When a translator is terminated, its memory accounting information is not destroyed as there could be some memory blocks referencing it still in use. However the mutexes that protect updates of the memory accounting are destroyed.

This causes that future updates of the accounting data may contend and do concurrent updates, causing corruption of the counters.

Additionally, accounting of reallocs is not correctly computed.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Xavi Hernandez 2019-04-23 11:55:51 UTC

This bug has been fixed as part of bug #1659334

*** This bug has been marked as a duplicate of bug 1659334 ***