Fix call_rcu fork handling
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Wed, 19 Dec 2012 00:31:21 +0000 (19:31 -0500)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Wed, 26 Dec 2012 17:05:54 +0000 (12:05 -0500)
commite85451a199f995091d2f740b6fd0ad2cd8fc2dc7
tree69215f5eebb3938f096d65c826ca4b059920d35b
parent390f0a26eb268ad42603a106866bacf6fb4a0649
Fix call_rcu fork handling

Fix call_rcu fork handling by putting all call_rcu threads in a
quiescent state before fork (paused state), and unpausing them when the
parent returns from fork.

On the child, everything will run fine as long as we don't issue fork()
from a call_rcu callback.

Side-note: pthread_atfork is not appropriate when using with multithread
and malloc/free. The glibc malloc implementation sadly expects that all
malloc/free are executed from the context of a single thread while
pthread atfork handlers are running, which leads to interesting hang in
glibc.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
urcu-call-rcu-impl.h
urcu-call-rcu.h
This page took 0.024927 seconds and 4 git commands to generate.