From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, will@kernel.org,
vincenzo.frascino@arm.com, sfr@canb.auug.org.au,
samitolvanen@google.com, ryabinin.a.a@gmail.com, pcc@google.com,
mark.rutland@arm.com, glider@google.com, fmayer@google.com,
eugenis@google.com, elver@google.com, dvyukov@google.com,
catalin.marinas@arm.com, andreyknvl@google.com,
akpm@linux-foundation.org
Subject: [to-be-updated] kasan-use-stack_trace_save_shadow.patch removed from -mm tree
Date: Thu, 31 Mar 2022 17:24:59 -0700 [thread overview]
Message-ID: <20220401002459.EE939C340F0@smtp.kernel.org> (raw)
The patch titled
Subject: kasan: use stack_trace_save_shadow
has been removed from the -mm tree. Its filename was
kasan-use-stack_trace_save_shadow.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
From: Andrey Konovalov <andreyknvl@google.com>
Subject: kasan: use stack_trace_save_shadow
Now that stack_trace_save_shadow() is implemented by arm64, use it
whenever CONFIG_HAVE_SHADOW_STACKTRACE is enabled. This improves the boot
time of a defconfig build by ~30% for all KASAN modes.
Link: https://lkml.kernel.org/r/7027b9b6b0cae2921ff65739582ae499bf61470c.1648049113.git.andreyknvl@google.com
Signed-off-by: Andrey Konovalov <andreyknvl@google.com>
Cc: Alexander Potapenko <glider@google.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Evgenii Stepanov <eugenis@google.com>
Cc: Florian Mayer <fmayer@google.com>
Cc: Marco Elver <elver@google.com>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Peter Collingbourne <pcc@google.com>
Cc: Sami Tolvanen <samitolvanen@google.com>
Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: Will Deacon <will@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/kasan/common.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
--- a/mm/kasan/common.c~kasan-use-stack_trace_save_shadow
+++ a/mm/kasan/common.c
@@ -33,10 +33,13 @@
depot_stack_handle_t kasan_save_stack(gfp_t flags, bool can_alloc)
{
unsigned long entries[KASAN_STACK_DEPTH];
- unsigned int nr_entries;
+ unsigned int size;
- nr_entries = stack_trace_save(entries, ARRAY_SIZE(entries), 0);
- return __stack_depot_save(entries, nr_entries, flags, can_alloc);
+ if (IS_ENABLED(CONFIG_HAVE_SHADOW_STACKTRACE))
+ size = stack_trace_save_shadow(entries, ARRAY_SIZE(entries), 0);
+ else
+ size = stack_trace_save(entries, ARRAY_SIZE(entries), 0);
+ return __stack_depot_save(entries, size, flags, can_alloc);
}
void kasan_set_track(struct kasan_track *track, gfp_t flags)
_
Patches currently in -mm which might be from andreyknvl@google.com are
mm-kasan-fix-__gfp_bits_shift-definition-breaking-lockdep.patch
reply other threads:[~2022-04-01 0:25 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=20220401002459.EE939C340F0@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=eugenis@google.com \
--cc=fmayer@google.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mm-commits@vger.kernel.org \
--cc=pcc@google.com \
--cc=ryabinin.a.a@gmail.com \
--cc=samitolvanen@google.com \
--cc=sfr@canb.auug.org.au \
--cc=vincenzo.frascino@arm.com \
--cc=will@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.