Bug 902174 - Race condition in unlink
Summary: Race condition in unlink
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: quick-read
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-21 05:20 UTC by Raghavendra G
Modified: 2013-07-24 17:12 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:12:56 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Raghavendra G 2013-01-21 05:20:52 UTC
Description of problem:

found this problem during code review. In qr_unlink, local->open_count is incremented by holding inode->lock. However, the same is decremented in qr_unlink_helper by holding a different lock (local->lock). This can result in a race-condition possibly leading to memory corruptions and other issues.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2013-02-07 22:41:53 UTC
CHANGE: http://review.gluster.org/4396 (performance/quick-read: fix race condition in unlink) merged in release-3.3 by Anand Avati (avati)


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