[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <167611145523.4906.11994571404061961204.tip-bot2@tip-bot2>
Date: Sat, 11 Feb 2023 10:30:55 -0000
From: "tip-bot2 for Peter Zijlstra" <tip-bot2@...utronix.de>
To: linux-tip-commits@...r.kernel.org
Cc: "Paul E. McKenney" <paulmck@...nel.org>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: [tip: sched/core] objtool: mem*() are not uaccess safe
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 443ed4c302fff6a26af980300463343a7adc9ee8
Gitweb: https://git.kernel.org/tip/443ed4c302fff6a26af980300463343a7adc9ee8
Author: Peter Zijlstra <peterz@...radead.org>
AuthorDate: Mon, 30 Jan 2023 15:21:02 +01:00
Committer: Peter Zijlstra <peterz@...radead.org>
CommitterDate: Sat, 11 Feb 2023 11:18:08 +01:00
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: 69d4c0d32186 ("entry, kasan, x86: Disallow overriding mem*() functions")
Reported-by: "Paul E. McKenney" <paulmck@...nel.org>
Bisected-by: Josh Poimboeuf <jpoimboe@...nel.org>
Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
Link: https://lkml.kernel.org/r/20230126182302.GA687063@paulmck-ThinkPad-P17-Gen-1
---
tools/objtool/check.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/tools/objtool/check.c b/tools/objtool/check.c
index 10b5bb4..b118f58 100644
--- a/tools/objtool/check.c
+++ b/tools/objtool/check.c
@@ -1083,9 +1083,6 @@ static const char *uaccess_safe_builtin[] = {
"__asan_store16_noabort",
"__kasan_check_read",
"__kasan_check_write",
- "__asan_memset",
- "__asan_memmove",
- "__asan_memcpy",
/* KASAN in-line */
"__asan_report_load_n_noabort",
"__asan_report_load1_noabort",
Powered by blists - more mailing lists