[Bugs] [Bug 1163822] New: Current timer implementation has no way to avoid some races

[bugzilla at redhat.com]

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

            Bug ID: 1163822
           Summary: Current timer implementation has no way to avoid some
                    races
           Product: GlusterFS
           Version: 3.6.0
         Component: core
          Assignee: bugs at gluster.org
          Reporter: xhernandez at datalab.es
                CC: bugs at gluster.org, gluster-bugs at redhat.com



+++ This bug was initially created as a clone of Bug #1163821 +++

Description of problem:

With the current implementation of timers in gluster, there are some situations
that cannot be handled in a safe way. This could lead to race conditions,
causing crashes or other unexpected side effects.

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

Additional info:

A clear example is the release of resources after cancelling a timer (the timer
could have not been really cancelled and the callback will run anyway but the
caller of gf_timer_call_cancel() has no way to know it).

Additionally, it's not possible to determine if a timer callback has been
executed or not, or synchronize with it and know if it has been executed
successfully.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.