From mboxrd@z Thu Jan 1 00:00:00 1970 From: Walter Wu Subject: Re: [PATCH v2 0/2] mm/kasan: dump alloc/free stack for page allocator Date: Tue, 10 Sep 2019 20:45:49 +0800 Message-ID: <1568119549.24886.18.camel@mtksdccf07> References: <20190909082412.24356-1-walter-zh.wu@mediatek.com> <4faedb4d-f16c-1917-9eaa-b0f9c169fa50@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4faedb4d-f16c-1917-9eaa-b0f9c169fa50@suse.cz> Sender: linux-kernel-owner@vger.kernel.org To: Vlastimil Babka Cc: Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov , Matthias Brugger , Andrew Morton , Martin Schwidefsky , Will Deacon , Andrey Konovalov , Arnd Bergmann , Thomas Gleixner , Michal Hocko , Qian Cai , linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, wsd_upstream@mediatek.com List-Id: linux-mediatek@lists.infradead.org On Tue, 2019-09-10 at 13:53 +0200, Vlastimil Babka wrote: > On 9/10/19 12:50 PM, Andrey Ryabinin wrote: > > > > > > For slab objects we memorize both alloc and free stacks. You'll never know in advance what information will be usefull > > to fix an issue, so it usually better to provide more information. I don't think we should do anything different for pages. > > Exactly, thanks. > > > Given that we already have the page_owner responsible for providing alloc/free stacks for pages, all that we should in KASAN do is to > > enable the feature by default. Free stack saving should be decoupled from debug_pagealloc into separate option so that it can be enabled > > by KASAN and/or debug_pagealloc. > > Right. Walter, can you do it that way, or should I? > > Thanks, > Vlastimil I will send new patch v3.