Bug 762265 (GLUSTER-533)

Summary: close() should not block main loop
Product: [Community] GlusterFS Reporter: Vikas Gorur <vikas>
Component: posixAssignee: Vikas Gorur <vikas>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: anush, avati, gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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().)