[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+fCnZekEu705yAX85wsCQeN21rk0tgS8ib6V8jrH_AscubbBA@mail.gmail.com>
Date: Sun, 20 Mar 2022 22:09:37 +0100
From: Andrey Konovalov <andreyknvl@...il.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: andrey.konovalov@...ux.dev, Marco Elver <elver@...gle.com>,
Alexander Potapenko <glider@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
kasan-dev <kasan-dev@...glegroups.com>,
Vincenzo Frascino <vincenzo.frascino@....com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Sami Tolvanen <samitolvanen@...gle.com>,
Peter Collingbourne <pcc@...gle.com>,
Evgenii Stepanov <eugenis@...gle.com>,
Linux Memory Management List <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrey Konovalov <andreyknvl@...gle.com>
Subject: Re: [PATCH] kasan, scs: collect stack traces from shadow stack
On Mon, Mar 14, 2022 at 8:17 AM Dmitry Vyukov <dvyukov@...gle.com> wrote:
>
> > +static unsigned int save_shadow_stack(unsigned long *entries,
> > + unsigned int nr_entries)
> > +{
> > + unsigned long *scs_sp = task_scs_sp(current);
> > + unsigned long *scs_base = task_scs(current);
>
> Just to double-check: interrupt frames are also appended to the the
> current task buffer, right?
Looked into this and found a few issues, will fix in v2. Interrupt
frames will be collected then.
Powered by blists - more mailing lists