Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1702271

Summary:	Memory accounting information is not always accurate
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	core	Assignee:	Xavi Hernandez <jahernan>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6	CC:	bugs, pasik
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:	1702268	Environment:
Last Closed:	2019-05-08 13:55:13 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:
Bug Depends On:	1659334, 1702268
Bug Blocks:

Description Xavi Hernandez 2019-04-23 11:35:31 UTC

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

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 Worker Ant 2019-04-23 11:55:22 UTC

REVIEW: https://review.gluster.org/22607 (core: handle memory accounting correctly) posted (#2) for review on release-6 by Xavi Hernandez

Comment 2 Worker Ant 2019-05-08 13:55:13 UTC

REVIEW: https://review.gluster.org/22607 (core: handle memory accounting correctly) merged (#2) on release-6 by Xavi Hernandez