Bug 762265 (GLUSTER-533) - close() should not block main loop
Summary: close() should not block main loop
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-533
Product: GlusterFS
Classification: Community
Component: posix
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Vikas Gorur
QA Contact:
URL:
Whiteboard:
: GLUSTER-566 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-12 09:58 UTC by Vikas Gorur
Modified: 2015-12-01 16:45 UTC (History)
3 users (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 2010-01-12 09:58:24 UTC 
close() is currently called in posix_release, which is called from the main
loop of the server. This can block the main loop. The job of calling close()
should be handed off to the janitor thread.
Comment 1 Anand Avati 2010-01-19 10:56:38 UTC 
PATCH: http://patches.gluster.com/patch/2660 in master (storage/posix: Hand off calling close() and closedir() to the janitor thread.)
Comment 2 Anand Avati 2010-01-21 09:25:49 UTC 
PATCH: http://patches.gluster.com/patch/2669 in master (storage/posix: Make the janitor sleep duration configurable.)
Comment 3 Anand Avati 2010-01-23 09:21:17 UTC 
*** Bug 566 has been marked as a duplicate of this bug. ***
Comment 4 Anand Avati 2010-01-25 09:32:30 UTC 
PATCH: http://patches.gluster.com/patch/2695 in master (storage/posix: Fix an access-after-free bug in release() and releasedir().)
Note You need to log in before you can comment on or make changes to this bug.