Update README for urcu-bp fork handling

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>

diff --git a/README b/README
index ec0d6a22b79c165a87cac300c6964e846f79c5a8..b6d2ae48d0b3365ccd0aa4344bc95f24ed6daef3 100644 (file)
--- a/README
+++ b/README
@@ -201,4 +201,6 @@ Interaction with fork()
        threads) should be released before a fork() is performed, except for the
        rather common scenario where fork() is immediately followed by exec() in
        the child process. The only implementation not subject to that rule is
-       liburcu-bp, which is designed to handle this case.
+       liburcu-bp, which is designed to handle this case by requiring a call to
+       synchronize_rcu() following the fork() in the child before any new
+       thread is created.