HBSD: Properly perform the write memory barrier

As reported by Alan Cox, Emmanuel Vadot's use and placing of wmb() was incorrect. Use the more appropriate function atomic_thread_fence_rel() at the more appropriate place. Signed-off-by: Shawn Webb <shawn.webb@hardenedbsd.org>
HardenedBSD · Aug 5, 2020 · e7ee745 · e7ee745
1 parent 4a6914c
commit e7ee745
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/sys/compat/linuxkpi/common/include/linux/bitops.h b/sys/compat/linuxkpi/common/include/linux/bitops.h
@@ -278,8 +278,8 @@ find_next_zero_bit(const unsigned long *addr, unsigned long size,
 static inline void
 clear_bit_unlock(long bit, volatile unsigned long *var)
 {
+	atomic_thread_fence_rel();
 	clear_bit(bit, var);
-	wmb();
 }
 
 static inline int