Bug 1805671

Summary:	Memory corruption when glfs_init() is called after glfs_fini()
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	core	Assignee:	Xavi Hernandez <jahernan>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6	CC:	bugs, pasik
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1801684	Environment:
Last Closed:	2020-02-28 06:12:35 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:	1801684
Bug Blocks:	1806846

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