All the atomic operations have volatile semantics to prevent compiler reordering. Enforce the same semantics for atomic_set() too.
Signed-off-by: Pranith Kumar <bobby.pr...@gmail.com> --- arch/x86/include/asm/atomic.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/include/asm/atomic.h b/arch/x86/include/asm/atomic.h index bf20c81..fa92e93 100644 --- a/arch/x86/include/asm/atomic.h +++ b/arch/x86/include/asm/atomic.h @@ -36,7 +36,7 @@ static inline int atomic_read(const atomic_t *v) */ static inline void atomic_set(atomic_t *v, int i) { - v->counter = i; + ACCESS_ONCE(v->counter) = i; } /** -- 2.1.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/