Bug 1702268 - Memory accounting information is not always accurate
Summary: Memory accounting information is not always accurate
Keywords:
Status: CLOSED DUPLICATE of bug 1659334
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1702270 1702271
TreeView+ depends on / blocked
 
Reported: 2019-04-23 11:23 UTC by Xavi Hernandez
Modified: 2019-04-23 11:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1702270 1702271 (view as bug list)
Environment:
Last Closed: 2019-04-23 11:55:51 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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 ***


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