X-Git-Url: http://git.liburcu.org/?p=urcu.git;a=blobdiff_plain;f=README;h=b6d2ae48d0b3365ccd0aa4344bc95f24ed6daef3;hp=ec0d6a22b79c165a87cac300c6964e846f79c5a8;hb=bfd123722c1b4f1eec58df9de60625efbb9ef23d;hpb=47c5a84f6137e1cb2fcbf448a134a0485d6f102e

diff --git a/README b/README
index ec0d6a2..b6d2ae4 100644
--- 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.