[Bugs] [Bug 1702271] New: Memory accounting information is not always accurate

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1702271

            Bug ID: 1702271
           Summary: Memory accounting information is not always accurate
           Product: GlusterFS
           Version: 6
            Status: NEW
         Component: core
          Assignee: bugs at gluster.org
          Reporter: jahernan at redhat.com
                CC: bugs at gluster.org
        Depends On: 1702268
            Blocks: 1702270
  Target Milestone: ---
    Classification: Community



+++ 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:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1702268
[Bug 1702268] Memory accounting information is not always accurate
https://bugzilla.redhat.com/show_bug.cgi?id=1702270
[Bug 1702270] Memory accounting information is not always accurate
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.