From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,ojeda@kernel.org,andreyknvl@gmail.com,akpm@linux-foundation.org
Subject: [folded-merged] kasan-simplify-and-clarify-makefile-v2.patch removed from -mm tree
Date: Tue, 03 Sep 2024 20:55:13 -0700 [thread overview]
Message-ID: <20240904035514.7956EC4CEC2@smtp.kernel.org> (raw)
The quilt patch titled
Subject: kasan-simplify-and-clarify-makefile-v2
has been removed from the -mm tree. Its filename was
kasan-simplify-and-clarify-makefile-v2.patch
This patch was dropped because it was folded into kasan-simplify-and-clarify-makefile.patch
------------------------------------------------------
From: Andrey Konovalov <andreyknvl@gmail.com>
Subject: kasan-simplify-and-clarify-makefile-v2
Date: Wed, 14 Aug 2024 18:10:52 +0200
comments fixes per Miguel
Link: https://lkml.kernel.org/r/20240814161052.10374-1-andrey.konovalov@linux.dev
Signed-off-by: Andrey Konovalov <andreyknvl@gmail.com>
Reviewed-by: Miguel Ojeda <ojeda@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
scripts/Makefile.kasan | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
--- a/scripts/Makefile.kasan~kasan-simplify-and-clarify-makefile-v2
+++ a/scripts/Makefile.kasan
@@ -34,13 +34,15 @@ endif
# First, enable -fsanitize=kernel-address together with providing the shadow
# mapping offset, as for GCC, -fasan-shadow-offset fails without -fsanitize
# (GCC accepts the shadow mapping offset via -fasan-shadow-offset instead of
-# a normal --param). Instead of ifdef-checking the compiler, rely on cc-option.
+# a --param like the other KASAN parameters).
+# Instead of ifdef-checking the compiler, rely on cc-option.
CFLAGS_KASAN := $(call cc-option, -fsanitize=kernel-address \
-fasan-shadow-offset=$(KASAN_SHADOW_OFFSET), \
$(call cc-option, -fsanitize=kernel-address \
-mllvm -asan-mapping-offset=$(KASAN_SHADOW_OFFSET)))
-# Now, add other parameters enabled in a similar way with GCC and Clang.
+# Now, add other parameters enabled similarly in both GCC and Clang.
+# As some of them are not supported by older compilers, use cc-param.
CFLAGS_KASAN += $(call cc-param,asan-instrumentation-with-call-threshold=$(call_threshold)) \
$(call cc-param,asan-stack=$(stack_enable)) \
$(call cc-param,asan-instrument-allocas=1) \
_
Patches currently in -mm which might be from andreyknvl@gmail.com are
kasan-simplify-and-clarify-makefile.patch
reply other threads:[~2024-09-04 3:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240904035514.7956EC4CEC2@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=mm-commits@vger.kernel.org \
--cc=ojeda@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.