From: Alexander Potapenko <glider@google.com>
To: Marco Elver <elver@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dmitry Vyukov <dvyukov@google.com>,
kasan-dev@googlegroups.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Feng Tang <feng.tang@intel.com>
Subject: Re: [PATCH] kfence: fix stack trace pruning
Date: Fri, 18 Nov 2022 18:09:19 +0100 [thread overview]
Message-ID: <CAG_fn=XGY6npNhVwK76zSZzYC61=7-8ag3Jcey4PXa46E1ee-A@mail.gmail.com> (raw)
In-Reply-To: <20221118152216.3914899-1-elver@google.com>
On Fri, Nov 18, 2022 at 4:22 PM Marco Elver <elver@google.com> wrote:
>
> Commit b14051352465 ("mm/sl[au]b: generalize kmalloc subsystem")
> refactored large parts of the kmalloc subsystem, resulting in the stack
> trace pruning logic done by KFENCE to no longer work.
>
> While b14051352465 attempted to fix the situation by including
> '__kmem_cache_free' in the list of functions KFENCE should skip through,
> this only works when the compiler actually optimized the tail call from
> kfree() to __kmem_cache_free() into a jump (and thus kfree() _not_
> appearing in the full stack trace to begin with).
>
> In some configurations, the compiler no longer optimizes the tail call
> into a jump, and __kmem_cache_free() appears in the stack trace. This
> means that the pruned stack trace shown by KFENCE would include kfree()
> which is not intended - for example:
>
> | BUG: KFENCE: invalid free in kfree+0x7c/0x120
> |
> | Invalid free of 0xffff8883ed8fefe0 (in kfence-#126):
> | kfree+0x7c/0x120
> | test_double_free+0x116/0x1a9
> | kunit_try_run_case+0x90/0xd0
> | [...]
>
> Fix it by moving __kmem_cache_free() to the list of functions that may
> be tail called by an allocator entry function, making the pruning logic
> work in both the optimized and unoptimized tail call cases.
>
> Fixes: b14051352465 ("mm/sl[au]b: generalize kmalloc subsystem")
> Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com>
> Cc: Feng Tang <feng.tang@intel.com>
> Signed-off-by: Marco Elver <elver@google.com>
Reviewed-by: Alexander Potapenko <glider@google.com>
> ---
> mm/kfence/report.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/mm/kfence/report.c b/mm/kfence/report.c
> index 7e496856c2eb..46ecea18c4ca 100644
> --- a/mm/kfence/report.c
> +++ b/mm/kfence/report.c
> @@ -75,18 +75,23 @@ static int get_stack_skipnr(const unsigned long stack_entries[], int num_entries
>
> if (str_has_prefix(buf, ARCH_FUNC_PREFIX "kfence_") ||
> str_has_prefix(buf, ARCH_FUNC_PREFIX "__kfence_") ||
> + str_has_prefix(buf, ARCH_FUNC_PREFIX "__kmem_cache_free") ||
> !strncmp(buf, ARCH_FUNC_PREFIX "__slab_free", len)) {
> /*
> - * In case of tail calls from any of the below
> - * to any of the above.
> + * In case of tail calls from any of the below to any of
> + * the above, optimized by the compiler such that the
> + * stack trace would omit the initial entry point below.
> */
> fallback = skipnr + 1;
> }
>
> - /* Also the *_bulk() variants by only checking prefixes. */
> + /*
> + * The below list should only include the initial entry points
> + * into the slab allocators. Includes the *_bulk() variants by
> + * checking prefixes.
> + */
> if (str_has_prefix(buf, ARCH_FUNC_PREFIX "kfree") ||
> str_has_prefix(buf, ARCH_FUNC_PREFIX "kmem_cache_free") ||
> - str_has_prefix(buf, ARCH_FUNC_PREFIX "__kmem_cache_free") ||
> str_has_prefix(buf, ARCH_FUNC_PREFIX "__kmalloc") ||
> str_has_prefix(buf, ARCH_FUNC_PREFIX "kmem_cache_alloc"))
> goto found;
> --
> 2.38.1.584.g0f3c55d4c2-goog
>
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straße, 33
80636 München
Geschäftsführer: Paul Manicle, Liana Sebastian
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
prev parent reply other threads:[~2022-11-18 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 15:22 Marco Elver
2022-11-18 17:09 ` Alexander Potapenko [this message]
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='CAG_fn=XGY6npNhVwK76zSZzYC61=7-8ag3Jcey4PXa46E1ee-A@mail.gmail.com' \
--to=glider@google.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=feng.tang@intel.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox