Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1315735

Summary:	Tier: Possible crash/undefined behaviour if thread creation fails
Product:	[Community] GlusterFS	Reporter:	Mohammed Rafi KC <rkavunga>
Component:	tiering	Assignee:	hari gowtham <hgowtham>
Status:	CLOSED DUPLICATE	QA Contact:	bugs <bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	bugs, mselvaga, prasanna.kalever
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-03 07:01:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mohammed Rafi KC 2016-03-08 13:46:32 UTC

Description of problem:

In tier_start, we  spawn two threads one for promotion and one for demotion. If the thread creation fails we do a join with out having a value for thread variabl. This can lead into a crash or undefined behaviour.

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

mainline

How reproducible:

Mosty

Steps to Reproduce:

1.create a tier volume
2.Attach tier process into gdb
3.using a break point try creating failure for thread creation in tier_start

Actual results:

crash
Expected results:

Should behave normally

Additional info:

Comment 1 Prasanna Kumar Kalever 2016-05-03 07:01:38 UTC


*** This bug has been marked as a duplicate of bug 1332219 ***