[Bugs] [Bug 1180231] glusterfs-fuse: Crash due to race in FUSE notify when multiple epoll threads invoke the routine

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1180231



--- Comment #4 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9421 committed in master by Raghavendra G
(rgowdapp at redhat.com) 
------
commit 3971315248c57386e05e6c8f57369a4571555cb2
Author: Shyam <srangana at redhat.com>
Date:   Thu Jan 8 13:56:08 2015 -0500

    fuse: Fix cores in notify function when this is executed in parallel

    The fuse notify function gets called by the epoll or the poll thread
    and till the point there is a single epoll thread, 2 notify
    instances would not race with each other.

    With the upcoming multi thread epoll changes, it is possible that
    2 epoll threads invoke the notify function. As a result races
    in this function are fixed with this commit.

    The races seen are detailed in the bug, and the fix here is to
    enforce a (slightly) longer critical section when updating the
    fuse private structure and reserving state updates post error
    handling.

    Change-Id: I6974bc043cb59eb6dc39c5777123364dcefca358
    BUG: 1180231
    Signed-off-by: Shyam <srangana at redhat.com>
    Reviewed-on: http://review.gluster.org/9421
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
    Tested-by: Raghavendra G <rgowdapp at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=B2m9NiZWpy&a=cc_unsubscribe