[Bugs] [Bug 1170643] Potential race while checking/updating graph->used

[bugzilla at redhat.com]

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



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9237 committed in master by Niels de Vos
(ndevos at redhat.com) 
------
commit 09af313fe6b49b03501939dd9e46b783ca4b5416
Author: Niels de Vos <ndevos at redhat.com>
Date:   Thu Dec 4 15:40:52 2014 +0100

    fuse: protect checking/modifying graph->used with a mutex

    While reviewing http://review.gluster.org/#/c/9060/ we noticed that fuse
    checks/modifies graph->used in a unlocked way. There is a potential race
    in case when fuse_graph_setup() gets called from two different threads
    (currently  unlikely, but poller/notify() might change in future?).

    In libgfapi we came to the conclusion that each glfs structure can be
    used to protect the checking/updating of graph->used. In fuse this would
    be the fuse_private_t with sync_mutex.

    BUG: 1170643
    Change-Id: If5ab5468d22fdb92cfb24a469f538f63f12baf78
    Signed-off-by: Niels de Vos <ndevos at redhat.com>
    Reviewed-on: http://review.gluster.org/9237
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-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=8gdRs1tjiN&a=cc_unsubscribe