Fix: missing rcu read locking in trigger "unregister all" command
authorJérémie Galarneau <jeremie.galarneau@efficios.com>
Wed, 23 Jan 2019 20:29:14 +0000 (15:29 -0500)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Wed, 23 Jan 2019 20:58:38 +0000 (15:58 -0500)
commit94223e306ae8c0ae0c625337317d779db6b30e0c
treea40ed9d3ed49303b695dd639b5e9eae89efe2940
parent2ff0b1187c79bb0b7615b0f372102e5e1620cc08
Fix: missing rcu read locking in trigger "unregister all" command

While the notification subsystem all runs within a single thread,
the iteration over the triggers hash table must be protected using
the RCU read-side lock since the RCU worker may resize the hash
table while the iteration is performed.

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