X-Git-Url: https://git.lttng.org/?a=blobdiff_plain;f=README;h=56e98d768e960ede0a80245a8a1a725218de33d4;hb=81ad2e193e8072f8246212d7eaba72769306c2e4;hp=b6d2ae48d0b3365ccd0aa4344bc95f24ed6daef3;hpb=bfd123722c1b4f1eec58df9de60625efbb9ef23d;p=urcu.git

diff --git a/README b/README
index b6d2ae4..56e98d7 100644
--- a/README
+++ b/README
@@ -201,6 +201,10 @@ 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 by requiring a call to
-	synchronize_rcu() following the fork() in the child before any new
-	thread is created.
+	liburcu-bp, which is designed to handle fork() by calling
+	rcu_bp_before_fork, rcu_bp_after_fork_parent and
+	rcu_bp_after_fork_child.
+
+	Applications that use call_rcu() are required to invoke
+	call_rcu_after_fork_child() from the child process after a
+	successful fork() system call that is not followed by exec().