diff options
author | Håkon Bugge <Haakon.Bugge@oracle.com> | 2017-07-20 12:28:55 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-07-20 15:33:01 -0700 |
commit | e623a48ee433985f6ca0fb238f0002cc2eccdf53 (patch) | |
tree | e3dc5acbe886b14e0dde4296b6b78748ac7175cd /block/blk-merge.c | |
parent | 070f9c658a59f9a736b1c040001d37b0952e778e (diff) |
rds: Make sure updates to cp_send_gen can be observed
cp->cp_send_gen is treated as a normal variable, although it may be
used by different threads.
This is fixed by using {READ,WRITE}_ONCE when it is incremented and
READ_ONCE when it is read outside the {acquire,release}_in_xmit
protection.
Normative reference from the Linux-Kernel Memory Model:
Loads from and stores to shared (but non-atomic) variables should
be protected with the READ_ONCE(), WRITE_ONCE(), and
ACCESS_ONCE().
Clause 5.1.2.4/25 in the C standard is also relevant.
Signed-off-by: Håkon Bugge <haakon.bugge@oracle.com>
Reviewed-by: Knut Omang <knut.omang@oracle.com>
Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'block/blk-merge.c')
0 files changed, 0 insertions, 0 deletions