Fix: semaphore semantics are expected from notification command eventfd
authorJérémie Galarneau <jeremie.galarneau@efficios.com>
Tue, 23 May 2017 14:15:59 +0000 (10:15 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Tue, 23 May 2017 14:15:59 +0000 (10:15 -0400)
commitd72c8834befc320e91576140ed0abace2eabbf7a
treeef1c455da0a1f8f42eacab0e031d1272f0b5c29a
parentce4d40839ac3beef1a58730d3636a522497bc60f
Fix: semaphore semantics are expected from notification command eventfd

The notification command queue currently expects eventfd() to
behave according to EFD_SEMAPHORE semantics. Right now, multiple
commands could be enqueued and reading the eventfd resets its
internal counter to 0. This will cause the notification thread
to never process the next command.

EFD_SEMAPHORE will ensure that poll/epoll signals that there is
info available for reading until the eventfd's internal counter
returns to 0.

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
src/bin/lttng-sessiond/notification-thread.c
This page took 0.034227 seconds and 4 git commands to generate.