diff options
author | Thomas Haller <thaller@redhat.com> | 2021-03-29 10:28:39 +0200 |
---|---|---|
committer | Thomas Haller <thaller@redhat.com> | 2021-03-29 10:48:30 +0200 |
commit | 7576f0c9bd4135f9b75bcd518c38e43f738638c5 (patch) | |
tree | 23b6be18d4ed07b91c42bacdda018202c9b6f43d | |
parent | 362a5aad21d7400bd208e1992b5a9d25473167e0 (diff) | |
download | NetworkManager-th/libnm-client-context.tar.gz |
libnm: add comment about context-busy-watcher and g_dbus_connection_signal_unsubscribe()th/libnm-client-context
-rw-r--r-- | src/libnm-client-impl/nm-client.c | 20 |
1 files changed, 19 insertions, 1 deletions
diff --git a/src/libnm-client-impl/nm-client.c b/src/libnm-client-impl/nm-client.c index 0382af6e41..641e8f67c0 100644 --- a/src/libnm-client-impl/nm-client.c +++ b/src/libnm-client-impl/nm-client.c @@ -7177,6 +7177,18 @@ nml_cleanup_context_busy_watcher_on_idle(GObject *context_busy_watcher_take, GMa * no destroy notify to g_dbus_connection_signal_subscribe(). * That means, there should be no other unaccounted GSource'es left. * + * Another reason is g_dbus_connection_signal_unsubscribe() which does + * not guarantee that everything was unsubscribe right away. Instead, + * there might still be idle actions queued (which will be thrown away + * once processed). Still, that means, the caller must continue to iterate + * the main context afterwards. Maybe we should pass a GDestroyNotify to + * g_dbus_connection_signal_subscribe() which handles an additional reference + * to the context_busy_watcher object. That would be the proper way to handle + * this. We don't do that, so in practice at this point there might still + * be some idle actions (with G_PRIORITY_DEFAULT) pending. As we schedule here + * another idle action with lower priority, we handle those cases without + * using a GDestroyNotify. + * * However, we really need to be sure that the context_busy_watcher's * lifetime matches the time that the context is busy. That is especially * important with synchronous initialization, where the context-busy-watcher @@ -7198,7 +7210,13 @@ nml_cleanup_context_busy_watcher_on_idle(GObject *context_busy_watcher_take, GMa * the user *MUST* always keep iterating the context after NMClient got destroyed. * But that is not a severe limitation, because the user anyway must be prepared * to do that. That is because in many cases it is necessary anyway (and the user - * wouldn't know a priory when not). This way, it is just always necessary. */ + * wouldn't know a priory when not). This way, it is just always necessary. + * + * It might be nice to use G_DEFAULT_PRIORITY here to minimize how long the + * instance stays alive. Probably that would be fine, even without passing + * a GDestroyNotify to g_dbus_connection_signal_subscribe(). But to be extra + * careful, use a low priority. + **/ cleanup_source = nm_g_idle_source_new(G_PRIORITY_LOW + 10, |