Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp2306247ybe; Thu, 12 Sep 2019 07:36:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqyfRfRo+7q36+x0YO4GjrV8u9h9XKfelNJ91p84qYHjSfBlpEdmxXX3lWhqvt8iIKFAAIrH X-Received: by 2002:a1c:be11:: with SMTP id o17mr270126wmf.93.1568299006259; Thu, 12 Sep 2019 07:36:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568299006; cv=none; d=google.com; s=arc-20160816; b=Lkqh3DKyVP+oCzYVTCP94cMQBkHUz7FZBxhK0OZEEYfgfTZu8IonWCMg383/U4xbpI DLwI7zEtyzvZGOh2aRmFXXbIzG7QiVuBTKKv9mSV1fAtNBiCK71BTZduUGOspF3++ghM 8kN6swF6Xhsmbq7hzalzM79KgTopppC1xghl4d564YdD+MaQUT/pMVQOxcvmYML4eRdt OcncXXisZ14GiX0QfoQ2WEfqH1Q/dGz5xrkeUkB3hzdYn1JOiQK0yD/krJs8mZTtnpfc 6GkioTgIq1/RmwMVYZqqk0ZYUDm7E+up1H0gyBgFGfrxXnflM6DPjSKuCxVthTMc9Bte cMeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=qCGzGglAEEQOOYCVDQldaZkHXNa1qIvCBD033Zjl6YQ=; b=cRSQUtu/h9wZdAAx+tvqZwpiIGZGGZQwK+sso/coFmBsfJ2XL+g9Tf10Vpe9j3YMVt yP7GdXr/sYD94236XHdT3nQSC7T17qk1EYE+wA1sY6DD/TAtKCDy7e91Fp/I4RVOFjWP A9M277xRf4J6dlslyJXByrrAqUFxxXX495jGMiNV/gahik6YsShEwaPmr2m0ty3KCKXj nQWGag/vZIpciHsqOW8m5pVotzV6mg9OENtBFgq21KtNts9Moi33ORrXnAmUmXHOr8KE eMjg+q3bTVPUOQV8LtLM9a3DJ5nxI1SnWaJBWw0rOhr8SSnSDRqyfowupc37ordCGoPk QcBA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k1si14780638ede.255.2019.09.12.07.36.21; Thu, 12 Sep 2019 07:36:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732689AbfILObp (ORCPT + 99 others); Thu, 12 Sep 2019 10:31:45 -0400 Received: from mx2.suse.de ([195.135.220.15]:40906 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1732579AbfILObo (ORCPT ); Thu, 12 Sep 2019 10:31:44 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id F35A4AFFE; Thu, 12 Sep 2019 14:31:42 +0000 (UTC) Subject: Re: [PATCH v3] mm/kasan: dump alloc and free stack for page allocator To: Walter Wu Cc: Qian Cai , Andrey Ryabinin , Alexander Potapenko , Dmitry Vyukov , Matthias Brugger , Andrew Morton , Martin Schwidefsky , Andrey Konovalov , Arnd Bergmann , 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 References: <20190911083921.4158-1-walter-zh.wu@mediatek.com> <5E358F4B-552C-4542-9655-E01C7B754F14@lca.pw> <1568297308.19040.5.camel@mtksdccf07> From: Vlastimil Babka Message-ID: <613f9f23-c7f0-871f-fe13-930c35ef3105@suse.cz> Date: Thu, 12 Sep 2019 16:31:42 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <1568297308.19040.5.camel@mtksdccf07> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/12/19 4:08 PM, Walter Wu wrote: > >> extern void __reset_page_owner(struct page *page, unsigned int order); >> diff --git a/lib/Kconfig.kasan b/lib/Kconfig.kasan >> index 6c9682ce0254..dc560c7562e8 100644 >> --- a/lib/Kconfig.kasan >> +++ b/lib/Kconfig.kasan >> @@ -41,6 +41,8 @@ config KASAN_GENERIC >> select SLUB_DEBUG if SLUB >> select CONSTRUCTORS >> select STACKDEPOT >> + select PAGE_OWNER >> + select PAGE_OWNER_FREE_STACK >> help >> Enables generic KASAN mode. >> Supported in both GCC and Clang. With GCC it requires version 4.9.2 >> @@ -63,6 +65,8 @@ config KASAN_SW_TAGS >> select SLUB_DEBUG if SLUB >> select CONSTRUCTORS >> select STACKDEPOT >> + select PAGE_OWNER >> + select PAGE_OWNER_FREE_STACK >> help > > What is the difference between PAGE_OWNER+PAGE_OWNER_FREE_STACK and > DEBUG_PAGEALLOC? Same memory usage, but debug_pagealloc means also extra checks and restricting memory access to freed pages to catch UAF. > If you directly enable PAGE_OWNER+PAGE_OWNER_FREE_STACK > PAGE_OWNER_FREE_STACK,don't you think low-memory device to want to use > KASAN? OK, so it should be optional? But I think it's enough to distinguish no PAGE_OWNER at all, and PAGE_OWNER+PAGE_OWNER_FREE_STACK together - I don't see much point in PAGE_OWNER only for this kind of debugging. So how about this? KASAN wouldn't select PAGE_OWNER* but it would be recommended in the help+docs. When PAGE_OWNER and KASAN are selected by user, PAGE_OWNER_FREE_STACK gets also selected, and both will be also runtime enabled without explicit page_owner=on. I mostly want to avoid another boot-time option for enabling PAGE_OWNER_FREE_STACK. Would that be enough flexibility for low-memory devices vs full-fledged debugging?