[Bugs] [Bug 1805668] New: Memory corruption when glfs_init() is called after glfs_fini()

[bugzilla at redhat.com]

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

            Bug ID: 1805668
           Summary: Memory corruption when glfs_init() is called after
                    glfs_fini()
           Product: GlusterFS
           Version: 7
            Status: NEW
         Component: core
          Keywords: Reopened
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: jahernan at redhat.com
                CC: bugs at gluster.org
        Depends On: 1801684
            Blocks: 1796628, 1800703
  Target Milestone: ---
    Classification: Community



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

Description of problem:

When a process calls glfs_fini(), some memory management structures are
destroyed. However the process might not finish after that. In that case, a new
call to glfs_init() won't fully reinitialize all structures for already running
threads, which can lead to memory corruption and crashes.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1796628
[Bug 1796628] gfapi: tcmu-runner receives SEGV on calling glfs_init() after
glfs_fini()
https://bugzilla.redhat.com/show_bug.cgi?id=1800703
[Bug 1800703] gfapi: SEGV on calling glfs_init() after glfs_fini()
https://bugzilla.redhat.com/show_bug.cgi?id=1801684
[Bug 1801684] Memory corruption when glfs_init() is called after glfs_fini()
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.