[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1567606591.32522.21.camel@mtksdccf07>
Date: Wed, 4 Sep 2019 22:16:31 +0800
From: Walter Wu <walter-zh.wu@...iatek.com>
To: Andrey Konovalov <andreyknvl@...gle.com>
CC: Andrey Ryabinin <aryabinin@...tuozzo.com>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Martin Schwidefsky" <schwidefsky@...ibm.com>,
Arnd Bergmann <arnd@...db.de>,
kasan-dev <kasan-dev@...glegroups.com>,
Linux Memory Management List <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>, <wsd_upstream@...iatek.com>
Subject: Re: [PATCH 1/2] mm/kasan: dump alloc/free stack for page allocator
On Wed, 2019-09-04 at 15:44 +0200, Andrey Konovalov wrote:
> On Wed, Sep 4, 2019 at 8:51 AM Walter Wu <walter-zh.wu@...iatek.com> wrote:
> > +config KASAN_DUMP_PAGE
> > + bool "Dump the page last stack information"
> > + depends on KASAN && PAGE_OWNER
> > + help
> > + By default, KASAN doesn't record alloc/free stack for page allocator.
> > + It is difficult to fix up page use-after-free issue.
> > + This feature depends on page owner to record the last stack of page.
> > + It is very helpful for solving the page use-after-free or out-of-bound.
>
> I'm not sure if we need a separate config for this. Is there any
> reason to not have this enabled by default?
PAGE_OWNER need some memory usage, it is not allowed to enable by
default in low RAM device. so I create new feature option and the person
who wants to use it to enable it.
Thanks.
Walter
Powered by blists - more mailing lists