From: Alexander Potapenko <glider@google.com>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Marco Elver <elver@google.com>,
Dmitriy Vyukov <dvyukov@google.com>,
Andrey Konovalov <andreyknvl@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [PATCH v2] mm/kasan: Print frame description for stack bugs
Date: Tue, 21 May 2019 17:52:55 +0200 [thread overview]
Message-ID: <CAG_fn=W+_Ft=g06wtOBgKnpD4UswE_XMXd61jw5ekOH_zeUVOQ@mail.gmail.com> (raw)
In-Reply-To: <ebec4325-f91b-b392-55ed-95dbd36bbb8e@virtuozzo.com>
On Tue, May 21, 2019 at 5:43 PM Andrey Ryabinin <aryabinin@virtuozzo.com> wrote:
>
>
>
> On 5/20/19 6:47 PM, Marco Elver wrote:
>
> > +static void print_decoded_frame_descr(const char *frame_descr)
> > +{
> > + /*
> > + * We need to parse the following string:
> > + * "n alloc_1 alloc_2 ... alloc_n"
> > + * where alloc_i looks like
> > + * "offset size len name"
> > + * or "offset size len name:line".
> > + */
> > +
> > + char token[64];
> > + unsigned long num_objects;
> > +
> > + if (!tokenize_frame_descr(&frame_descr, token, sizeof(token),
> > + &num_objects))
> > + return;
> > +
> > + pr_err("\n");
> > + pr_err("this frame has %lu %s:\n", num_objects,
> > + num_objects == 1 ? "object" : "objects");
> > +
> > + while (num_objects--) {
> > + unsigned long offset;
> > + unsigned long size;
> > +
> > + /* access offset */
> > + if (!tokenize_frame_descr(&frame_descr, token, sizeof(token),
> > + &offset))
> > + return;
> > + /* access size */
> > + if (!tokenize_frame_descr(&frame_descr, token, sizeof(token),
> > + &size))
> > + return;
> > + /* name length (unused) */
> > + if (!tokenize_frame_descr(&frame_descr, NULL, 0, NULL))
> > + return;
> > + /* object name */
> > + if (!tokenize_frame_descr(&frame_descr, token, sizeof(token),
> > + NULL))
> > + return;
> > +
> > + /* Strip line number, if it exists. */
>
> Why?
>
> > + strreplace(token, ':', '\0');
> > +
>
> ...
>
> > +
> > + aligned_addr = round_down((unsigned long)addr, sizeof(long));
> > + mem_ptr = round_down(aligned_addr, KASAN_SHADOW_SCALE_SIZE);
> > + shadow_ptr = kasan_mem_to_shadow((void *)aligned_addr);
> > + shadow_bottom = kasan_mem_to_shadow(end_of_stack(current));
> > +
> > + while (shadow_ptr >= shadow_bottom && *shadow_ptr != KASAN_STACK_LEFT) {
> > + shadow_ptr--;
> > + mem_ptr -= KASAN_SHADOW_SCALE_SIZE;
> > + }
> > +
> > + while (shadow_ptr >= shadow_bottom && *shadow_ptr == KASAN_STACK_LEFT) {
> > + shadow_ptr--;
> > + mem_ptr -= KASAN_SHADOW_SCALE_SIZE;
> > + }
> > +
>
> I suppose this won't work if stack grows up, which is fine because it grows up only on parisc arch.
> But "BUILD_BUG_ON(IS_ENABLED(CONFIG_STACK_GROUWSUP))" somewhere wouldn't hurt.
Note that KASAN was broken on parisc from day 1 because of other
assumptions on the stack growth direction hardcoded into KASAN
(e.g. __kasan_unpoison_stack() and __asan_allocas_unpoison()).
So maybe this BUILD_BUG_ON can be added in a separate patch as it's
not specific to what Marco is doing here?
>
> --
> You received this message because you are subscribed to the Google Groups "kasan-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to kasan-dev+unsubscribe@googlegroups.com.
> To post to this group, send email to kasan-dev@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kasan-dev/ebec4325-f91b-b392-55ed-95dbd36bbb8e%40virtuozzo.com.
> For more options, visit https://groups.google.com/d/optout.
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straße, 33
80636 München
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
next prev parent reply other threads:[~2019-05-21 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 15:47 Marco Elver
2019-05-21 15:43 ` Andrey Ryabinin
2019-05-21 15:52 ` Alexander Potapenko [this message]
2019-05-21 16:07 ` Marco Elver
2019-05-21 18:07 ` Andrey Ryabinin
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=W+_Ft=g06wtOBgKnpD4UswE_XMXd61jw5ekOH_zeUVOQ@mail.gmail.com' \
--to=glider@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=elver@google.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