luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-25 23:16:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

gcancellable: allow g_cancellable_disconnect from "cancelled" handler on same thread

Browse Source 
g_cancellable_disconnect will wait until any pending "cancelled"
handlers finish.  This is useful because disconnecting a handler can have the
side-effect of freeing data that the cancelled handler may rely on.
Unfortunately, the code used to enforce this synchronization between
"cancelled" handlers and g_cancellable_disconnect will also cause
deadlock if the cancelled handler itself calls g_cancellable_disconect.

Obviously, if g_cancellable_disconnect is explicitly called by a "cancelled"
handler, then the "cancelled" handler is shouldering the responsibility
of not using any data that may be freed by disconnection.

Also, g_cancellable_disconnect can be called in unexpected places by
lower layers in the code (for instance as a result of g_source_destroy).
In practice, this means it's easy for deadlocks to inadvertently crop
up when using "cancelled" handlers.

For these reasons, it would be good to fix the deadlock.

This commit prevents the deadlock by allowing foregoing synchronization,
if a pending "cancelled" handler is in the same thread as the
g_cancellabale_disconnnect call.

https://bugzilla.gnome.org/show_bug.cgi?id=705395
This commit is contained in:
Ray Strode 2013-09-10 15:32:12 -04:00 committed by Alexander Larsson
parent 795a36142d
commit 83605e2d0a
1 changed files with 19 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
gio/gcancellable.c
View File

@ -46,8 +46,8 @@ enum {
struct _GCancellablePrivate
{
guint cancelled : 1;
guint cancelled_running : 1;
guint cancelled_running_waiting : 1;
GThread *cancelled_running_thread;
guint fd_refcount;
GWakeup *wakeup;
@ -260,7 +260,8 @@ g_cancellable_reset (GCancellable *cancellable)
priv = cancellable->priv;
while (priv->cancelled_running)
while (priv->cancelled_running_thread != NULL &&
priv->cancelled_running_thread != g_thread_self ())
{
priv->cancelled_running_waiting = TRUE;
g_cond_wait (&cancellable_cond, &cancellable_mutex);
@ -492,7 +493,7 @@ g_cancellable_cancel (GCancellable *cancellable)
}
priv->cancelled = TRUE;
priv->cancelled_running = TRUE;
priv->cancelled_running_thread = g_thread_self ();
if (priv->wakeup)
GLIB_PRIVATE_CALL (g_wakeup_signal) (priv->wakeup);
@ -504,7 +505,7 @@ g_cancellable_cancel (GCancellable *cancellable)
g_mutex_lock (&cancellable_mutex);
priv->cancelled_running = FALSE;
priv->cancelled_running_thread = NULL;
if (priv->cancelled_running_waiting)
g_cond_broadcast (&cancellable_cond);
priv->cancelled_running_waiting = FALSE;
@ -557,6 +558,8 @@ g_cancellable_connect (GCancellable *cancellable,
void (*_callback) (GCancellable *cancellable,
gpointer user_data);
g_mutex_unlock (&cancellable_mutex);
_callback = (void *)callback;
id = 0;
@ -571,9 +574,10 @@ g_cancellable_connect (GCancellable *cancellable,
callback, data,
(GClosureNotify) data_destroy_func,
0);
}
g_mutex_unlock (&cancellable_mutex);
}
return id;
}
@ -585,16 +589,19 @@ g_cancellable_connect (GCancellable *cancellable,
*
* Disconnects a handler from a cancellable instance similar to
* g_signal_handler_disconnect(). Additionally, in the event that a
* signal handler is currently running, this call will block until the
* handler has finished. Calling this function from a
* #GCancellable::cancelled signal handler will therefore result in a
* deadlock.
* signal handler is currently running on a different thread, this
* call will block until the handler has finished.
*
* This avoids a race condition where a thread cancels at the
* same time as the cancellable operation is finished and the
* signal handler is removed. See #GCancellable::cancelled for
* details on how to use this.
*
* Note, since 2.38 it is safe to call this function from a
* #GCancellable::cancelled signal handler, something which would
* previously have caused a deadlock. However, it is not a good idea
* to disconnect a signal handler from inside its *own* signal handler.
*
* If @cancellable is %NULL or @handler_id is %0 this function does
* nothing.
*
@ -613,7 +620,8 @@ g_cancellable_disconnect (GCancellable *cancellable,
priv = cancellable->priv;
while (priv->cancelled_running)
while (priv->cancelled_running_thread != NULL &&
priv->cancelled_running_thread != g_thread_self ())
{
priv->cancelled_running_waiting = TRUE;
g_cond_wait (&cancellable_cond, &cancellable_mutex);