提交 443ed4c3 编写于 作者: P Peter Zijlstra

objtool: mem*() are not uaccess safe

For mysterious raisins I listed the new __asan_mem*() functions as
being uaccess safe, this is giving objtool fails on KASAN builds
because these functions call out to the actual __mem*() functions
which are not marked uaccess safe.

Removing it doesn't make the robots unhappy.

Fixes: 69d4c0d3 ("entry, kasan, x86: Disallow overriding mem*() functions")
Reported-by: N"Paul E. McKenney" <paulmck@kernel.org>
Bisected-by: NJosh Poimboeuf <jpoimboe@kernel.org>
Signed-off-by: NPeter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20230126182302.GA687063@paulmck-ThinkPad-P17-Gen-1
上级 4d627628
...@@ -1083,9 +1083,6 @@ static const char *uaccess_safe_builtin[] = { ...@@ -1083,9 +1083,6 @@ static const char *uaccess_safe_builtin[] = {
"__asan_store16_noabort", "__asan_store16_noabort",
"__kasan_check_read", "__kasan_check_read",
"__kasan_check_write", "__kasan_check_write",
"__asan_memset",
"__asan_memmove",
"__asan_memcpy",
/* KASAN in-line */ /* KASAN in-line */
"__asan_report_load_n_noabort", "__asan_report_load_n_noabort",
"__asan_report_load1_noabort", "__asan_report_load1_noabort",
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册