documentation: Subsequent writes ordered by rcu_dereference()
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Thu, 14 Jan 2016 22:17:04 +0000 (14:17 -0800)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Mon, 14 Mar 2016 22:52:17 +0000 (15:52 -0700)
commit92a84dd210b8263f765882d3ee1a1d5cd348c16a
tree84336d89daf350394d408b908363e6d29d3ff89c
parent0e4bd2aba3d0ae5caeb0d1a2b71f6fe6147c4d56
documentation: Subsequent writes ordered by rcu_dereference()

The current memory-barriers.txt does not address the possibility of
a write to a dereferenced pointer.  This should be rare, but when it
happens, we need that write -not- to be clobbered by the initialization.
This commit therefore adds an example showing a data dependency ordering
a later data-dependent write.

Reported-by: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Documentation/memory-barriers.txt