From: Walter Wu <walter-zh.wu@mediatek•com>
To: Qian Cai <cai@lca•pw>
Cc: wsd_upstream@mediatek•com, Arnd Bergmann <arnd@arndb•de>,
Linux Memory Management List <linux-mm@kvack•org>,
LKML <linux-kernel@vger•kernel.org>,
kasan-dev <kasan-dev@googlegroups•com>,
Martin Schwidefsky <schwidefsky@de•ibm.com>,
linux-mediatek@lists•infradead.org,
Linux ARM <linux-arm-kernel@lists•infradead.org>,
Andrey Ryabinin <aryabinin@virtuozzo•com>,
Matthias Brugger <matthias.bgg@gmail•com>,
Alexander Potapenko <glider@google•com>,
Andrew Morton <akpm@linux-foundation•org>,
Dmitry Vyukov <dvyukov@google•com>
Subject: Re: [PATCH 1/2] mm/kasan: dump alloc/free stack for page allocator
Date: Thu, 5 Sep 2019 09:54:36 +0800 [thread overview]
Message-ID: <1567648476.32522.36.camel@mtksdccf07> (raw)
In-Reply-To: <1567607824.5576.77.camel@lca.pw>
On Wed, 2019-09-04 at 10:37 -0400, Qian Cai wrote:
> On Wed, 2019-09-04 at 22:16 +0800, Walter Wu wrote:
> > 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@mediatek•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.
>
> Or you can try to look into reducing the memory footprint of PAGE_OWNER to fit
> your needs. It does not always need to be that way.
Thanks your suggestion. We can try to think what can be slimmed.
Thanks.
Walter
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-09-05 1:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 6:51 [PATCH 1/2] mm/kasan: dump alloc/free stack for page allocator Walter Wu
2019-09-04 12:49 ` Vlastimil Babka
2019-09-04 14:06 ` Walter Wu
2019-09-04 14:13 ` Vlastimil Babka
2019-09-04 14:24 ` Walter Wu
2019-09-05 8:03 ` Vlastimil Babka
2019-09-06 3:15 ` Walter Wu
2019-09-04 13:44 ` Andrey Konovalov
2019-09-04 14:16 ` Walter Wu
2019-09-04 14:37 ` Qian Cai
2019-09-05 1:54 ` Walter Wu [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=1567648476.32522.36.camel@mtksdccf07 \
--to=walter-zh.wu@mediatek$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=aryabinin@virtuozzo$(echo .)com \
--cc=cai@lca$(echo .)pw \
--cc=dvyukov@google$(echo .)com \
--cc=glider@google$(echo .)com \
--cc=kasan-dev@googlegroups$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mediatek@lists$(echo .)infradead.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=matthias.bgg@gmail$(echo .)com \
--cc=schwidefsky@de$(echo .)ibm.com \
--cc=wsd_upstream@mediatek$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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