Bug 1805671 - Memory corruption when glfs_init() is called after glfs_fini()
Summary: Memory corruption when glfs_init() is called after glfs_fini()
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: 6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Xavi Hernandez
QA Contact:
URL:
Whiteboard:
Depends On: 1801684
Blocks: 1806846
TreeView+ depends on / blocked
 
Reported: 2020-02-21 10:56 UTC by Xavi Hernandez
Modified: 2020-03-02 07:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1801684
Environment:
Last Closed: 2020-02-28 06:12:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 24159 0 None Merged core: fix memory pool management races 2020-02-28 06:12:34 UTC

Description Xavi Hernandez 2020-02-21 10:56:26 UTC 
+++ 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:
Comment 1 Worker Ant 2020-02-21 11:06:12 UTC 
REVIEW: https://review.gluster.org/24159 (core: fix memory pool management races) posted (#1) for review on release-6 by Xavi Hernandez
Comment 2 Worker Ant 2020-02-28 06:12:35 UTC 
REVIEW: https://review.gluster.org/24159 (core: fix memory pool management races) merged (#2) on release-6 by hari gowtham
Note You need to log in before you can comment on or make changes to this bug.