From: Mathieu Desnoyers Date: Wed, 12 Dec 2018 22:37:54 +0000 (-0500) Subject: Fix: do not repurpose iterator while it is being used X-Git-Tag: v2.10.6~6 X-Git-Url: https://git.lttng.org./?a=commitdiff_plain;h=88c6cf5e08792a86853a27b94944dc9df1d3a330;p=lttng-tools.git Fix: do not repurpose iterator while it is being used The hash table iteration uses an iterator that needs to stay valid for the next loop. Using that same iterator variable in a nested lookup in a different hash table leads to segmentation fault. This is a 2.10-specific instance of the issue affecting bind_trigger_to_matching_channels() which was found in the master and 2.11 branches. This one affects handle_notification_thread_command_register_trigger(). Signed-off-by: Mathieu Desnoyers Signed-off-by: Jérémie Galarneau --- diff --git a/src/bin/lttng-sessiond/notification-thread-events.c b/src/bin/lttng-sessiond/notification-thread-events.c index 6777fd6dd..f54141e73 100644 --- a/src/bin/lttng-sessiond/notification-thread-events.c +++ b/src/bin/lttng-sessiond/notification-thread-events.c @@ -1119,6 +1119,7 @@ int handle_notification_thread_command_register_trigger( channels_ht_node) { struct lttng_trigger_list_element *trigger_list_element; struct lttng_channel_trigger_list *trigger_list; + struct cds_lfht_iter lookup_iter; if (!trigger_applies_to_channel(trigger, channel)) { continue; @@ -1128,8 +1129,8 @@ int handle_notification_thread_command_register_trigger( hash_channel_key(&channel->key), match_channel_trigger_list, &channel->key, - &iter); - node = cds_lfht_iter_get_node(&iter); + &lookup_iter); + node = cds_lfht_iter_get_node(&lookup_iter); assert(node); trigger_list = caa_container_of(node, struct lttng_channel_trigger_list,