X-Git-Url: https://git.lttng.org/?p=lttng-tools.git;a=blobdiff_plain;f=src%2Fbin%2Flttng-sessiond%2Fnotification-thread.h;h=8b4c7af2b0326dec1126ea2767cc1ffcf0e9761c;hp=83a5bea79e175240b462e0703c743220ee98ba02;hb=8b5240601e4ddf6127e4291b7194dd5179cb35b5;hpb=b9a8d78fefbc856370939d9eb553d6e9c1fcc86a

diff --git a/src/bin/lttng-sessiond/notification-thread.h b/src/bin/lttng-sessiond/notification-thread.h
index 83a5bea79..8b4c7af2b 100644
--- a/src/bin/lttng-sessiond/notification-thread.h
+++ b/src/bin/lttng-sessiond/notification-thread.h
@@ -285,6 +285,31 @@ struct notification_thread_state {
 	struct cds_list_head tracer_event_sources_list;
 	notification_client_id next_notification_client_id;
 	struct action_executor *executor;
+
+	/*
+	 * Indicates the thread to break for the poll event processing loop and
+	 * call _poll_wait() again.
+	 *
+	 * This is necessary because some events on one fd might trigger the
+	 * consumption of another fd.
+	 * For example, a single _poll_wait() call can return notification
+	 * thread commands and events from the tracer event source (event
+	 * notifier).
+	 * Picture a scenario where we receive two events:
+	 *  the first one is a _REMOVE_TRACER_EVENT_SOURCE command, and
+	 *  the second is an POLLIN on the tracer event source fd.
+	 *
+	 * The _REMOVE_TRACER_EVENT_SOURCE will read all the data of the
+	 * removed tracer event source.
+	 *
+	 * The second event is now invalid has we consumed all the data for
+	 * which we received the POLLIN.
+	 *
+	 * For this reason, we need to break for the event processing loop and
+	 * call _poll_wait() again to get a clean view of the activity on the
+	 * fds.
+	 */
+	bool restart_poll;
 };
 
 /* notification_thread_data takes ownership of the channel monitor pipes. */