Fix: protect the channel's metadata stream using the metadata cache lock
authorJérémie Galarneau <jeremie.galarneau@efficios.com>
Wed, 21 Dec 2016 22:56:24 +0000 (17:56 -0500)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Fri, 6 Jan 2017 16:38:19 +0000 (11:38 -0500)
commit6ba5305c8ec548191f30c9e0c540faeb1977252a
tree903c23e731787963a9269530e6b3849609c9f7de
parent87f05398efb9985607b1a312f58abfaee2ecc453
Fix: protect the channel's metadata stream using the metadata cache lock

The consumer_thread_data_poll and consumer_thread_metadata_poll
both access the channel's metadata stream.

During a session destruction, consumer_thread_metadata_poll will
destroy all metadata streams. However, the consumer_thread_data_poll
may still invoke a consumer_metadata_cache_write() triggered
by a "ready" subbuffer. Hence, the metadata stream must be protected
from this action by the metadata cache lock.

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
src/common/consumer/consumer-metadata-cache.c
src/common/consumer/consumer.c
This page took 0.024717 seconds and 4 git commands to generate.