[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240511144436754EiKfJM4xjMSTyCbEExwcL@zte.com.cn>
Date: Sat, 11 May 2024 14:44:36 +0800 (CST)
From: <xu.xin16@....com.cn>
To: <akpm@...ux-foundation.org>
Cc: <david@...hat.com>, <willy@...radead.org>, <shy828301@...il.com>,
<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>, <ziy@...dia.com>
Subject: [PATCH linux-next] mm/huge_memory: mark racy access on huge_anon_orders_always
From: Ran Xiaokai <ran.xiaokai@....com.cn>
huge_anon_orders_always and huge_anon_orders_always are accessed
lockless, it is better to use the READ_ONCE() wrapper.
This is not fixing any visible bug, hopefully this can cease some
KCSAN complains in the future.
Also do that for huge_anon_orders_madvise.
Signed-off-by: Ran Xiaokai <ran.xiaokai@....com.cn>
---
include/linux/huge_mm.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/huge_mm.h b/include/linux/huge_mm.h
index de0c89105076..6573430ea600 100644
--- a/include/linux/huge_mm.h
+++ b/include/linux/huge_mm.h
@@ -122,8 +122,8 @@ static inline bool hugepage_flags_enabled(void)
* So we don't need to look at huge_anon_orders_inherit.
*/
return hugepage_global_enabled() ||
- huge_anon_orders_always ||
- huge_anon_orders_madvise;
+ READ_ONCE(huge_anon_orders_always) ||
+ READ_ONCE(huge_anon_orders_madvise);
}
static inline int highest_order(unsigned long orders)
--
2.15.2
Powered by blists - more mailing lists