Bug 762126 (GLUSTER-394) - Possible deadlock in _gf_log
Summary: Possible deadlock in _gf_log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-394
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Vikas Gorur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-18 10:48 UTC by Vikas Gorur
Modified: 2009-11-24 09:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Vikas Gorur 2009-11-18 10:48:56 UTC 
_gf_log jumps to "out" if asprintf or vaprintf fail, without unlocking the mutex. This can result in a deadlock.
Comment 1 Anand Avati 2009-11-18 10:56:01 UTC 
PATCH: http://patches.gluster.com/patch/2297 in master (libglusterfs: Fix error handling in _gf_log.)
Note You need to log in before you can comment on or make changes to this bug.