Bug 1315735 - Tier: Possible crash/undefined behaviour if thread creation fails
Summary: Tier: Possible crash/undefined behaviour if thread creation fails
Keywords:
Status: CLOSED DUPLICATE of bug 1332219
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: mainline
Hardware: All
OS: Unspecified
high
high
Target Milestone: ---
Assignee: hari gowtham
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-08 13:46 UTC by Mohammed Rafi KC
Modified: 2016-05-03 07:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-03 07:01:38 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.