Fix: rcutorture: work-around signal issue on mac os x
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 8 Sep 2016 02:11:53 +0000 (22:11 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 8 Sep 2016 02:14:26 +0000 (22:14 -0400)
commit6051170c57a486a5934f1b0b9ec40464d980ae78
tree041dc83a44a1fc428dcab5e9514a71c8e0d470a9
parentfcb81146d096d63d39adde4f790465a5c52999bb
Fix: rcutorture: work-around signal issue on mac os x

Our MacOS X test machine with the following config:

15.6.0 Darwin Kernel Version 15.6.0
root:xnu-3248.60.10~1/RELEASE_X86_64

appears to have issues with liburcu-signal signal being delivered on top
of pthread_cond_wait. It seems to make the thread continue, and
therefore corrupt the rcu_head. Work around this issue by unregistering
the RCU read-side thread immediately after call_rcu (call_rcu needs us
to be registered RCU readers).

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
tests/regression/rcutorture.h
This page took 0.025462 seconds and 4 git commands to generate.