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:34:11 +0000 (15:34 -0500)
commit6bfc8da05c035890b24a6563647ad35afeee0ed8
treeb3fa10906e69be81375e1dbe1a2afb034404bcc8
parent0fe4c3bf415eef3325b53383cbc3bc087db55d7f
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.027084 seconds and 5 git commands to generate.