diff options
| author | Alan Stern <stern@rowland.harvard.edu> | 2019-06-20 11:55:36 -0400 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@linux.ibm.com> | 2019-06-21 16:18:45 -0700 |
| commit | f9de417121001879d92a86960647adb06b5b81bf (patch) | |
| tree | e194fde88ab826f0f05995c3d94a52c9c41664c4 /crypto | |
| parent | 37c600a3cc8a6941d77e853ec4e0e33fffa1046b (diff) | |
tools/memory-model: Expand definition of barrier
Commit 66be4e66a7f4 ("rcu: locking and unlocking need to always be at
least barriers") added compiler barriers back into rcu_read_lock() and
rcu_read_unlock(). Furthermore, srcu_read_lock() and
srcu_read_unlock() have always contained compiler barriers.
The Linux Kernel Memory Model ought to know about these barriers.
This patch adds them into the memory model.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Acked-by: Andrea Parri <andrea.parri@amarulasolutions.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.ibm.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions