From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-9.7 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9EE81C5519F for ; Mon, 16 Nov 2020 12:16:14 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id EA6EF2224B for ; Mon, 16 Nov 2020 12:16:13 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EA6EF2224B Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=arm.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 4DF326B0036; Mon, 16 Nov 2020 07:16:13 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 469166B005D; Mon, 16 Nov 2020 07:16:13 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3306A6B0068; Mon, 16 Nov 2020 07:16:13 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0184.hostedemail.com [216.40.44.184]) by kanga.kvack.org (Postfix) with ESMTP id 024436B0036 for ; Mon, 16 Nov 2020 07:16:12 -0500 (EST) Received: from smtpin15.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id A19E1180AD81D for ; Mon, 16 Nov 2020 12:16:12 +0000 (UTC) X-FDA: 77490178584.15.cast34_4a16b8127328 Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin15.hostedemail.com (Postfix) with ESMTP id 79E331814B0C7 for ; Mon, 16 Nov 2020 12:16:12 +0000 (UTC) X-HE-Tag: cast34_4a16b8127328 X-Filterd-Recvd-Size: 6784 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf30.hostedemail.com (Postfix) with ESMTP for ; Mon, 16 Nov 2020 12:16:11 +0000 (UTC) Received: from trantor (unknown [2.26.170.190]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A17A622263; Mon, 16 Nov 2020 12:16:07 +0000 (UTC) Date: Mon, 16 Nov 2020 12:16:05 +0000 From: Catalin Marinas To: Marco Elver Cc: Dmitry Vyukov , Andrey Konovalov , Will Deacon , Vincenzo Frascino , Alexander Potapenko , Evgenii Stepanov , Kostya Serebryany , Peter Collingbourne , Serban Constantinescu , Andrey Ryabinin , Elena Petrova , Branislav Rankov , Kevin Brodsky , Andrew Morton , kasan-dev , Linux ARM , Linux-MM , LKML Subject: Re: [PATCH RFC v2 04/21] kasan: unpoison stack only with CONFIG_KASAN_STACK Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, Nov 16, 2020 at 12:50:00PM +0100, Marco Elver wrote: > On Mon, 16 Nov 2020 at 11:59, Dmitry Vyukov wrote: > > On Thu, Oct 29, 2020 at 8:57 PM 'Andrey Konovalov' via kasan-dev > > wrote: > > > On Tue, Oct 27, 2020 at 1:44 PM Dmitry Vyukov wrote: > > > > > > > > On Thu, Oct 22, 2020 at 3:19 PM Andrey Konovalov wrote: > > > > > > > > > > There's a config option CONFIG_KASAN_STACK that has to be enabled for > > > > > KASAN to use stack instrumentation and perform validity checks for > > > > > stack variables. > > > > > > > > > > There's no need to unpoison stack when CONFIG_KASAN_STACK is not enabled. > > > > > Only call kasan_unpoison_task_stack[_below]() when CONFIG_KASAN_STACK is > > > > > enabled. > > > > > > > > > > Signed-off-by: Andrey Konovalov > > > > > Link: https://linux-review.googlesource.com/id/If8a891e9fe01ea543e00b576852685afec0887e3 > > > > > --- > > > > > arch/arm64/kernel/sleep.S | 2 +- > > > > > arch/x86/kernel/acpi/wakeup_64.S | 2 +- > > > > > include/linux/kasan.h | 10 ++++++---- > > > > > mm/kasan/common.c | 2 ++ > > > > > 4 files changed, 10 insertions(+), 6 deletions(-) > > > > > > > > > > diff --git a/arch/arm64/kernel/sleep.S b/arch/arm64/kernel/sleep.S > > > > > index ba40d57757d6..bdadfa56b40e 100644 > > > > > --- a/arch/arm64/kernel/sleep.S > > > > > +++ b/arch/arm64/kernel/sleep.S > > > > > @@ -133,7 +133,7 @@ SYM_FUNC_START(_cpu_resume) > > > > > */ > > > > > bl cpu_do_resume > > > > > > > > > > -#ifdef CONFIG_KASAN > > > > > +#if defined(CONFIG_KASAN) && CONFIG_KASAN_STACK > > > > > mov x0, sp > > > > > bl kasan_unpoison_task_stack_below > > > > > #endif > > > > > diff --git a/arch/x86/kernel/acpi/wakeup_64.S b/arch/x86/kernel/acpi/wakeup_64.S > > > > > index c8daa92f38dc..5d3a0b8fd379 100644 > > > > > --- a/arch/x86/kernel/acpi/wakeup_64.S > > > > > +++ b/arch/x86/kernel/acpi/wakeup_64.S > > > > > @@ -112,7 +112,7 @@ SYM_FUNC_START(do_suspend_lowlevel) > > > > > movq pt_regs_r14(%rax), %r14 > > > > > movq pt_regs_r15(%rax), %r15 > > > > > > > > > > -#ifdef CONFIG_KASAN > > > > > +#if defined(CONFIG_KASAN) && CONFIG_KASAN_STACK > > > > > /* > > > > > * The suspend path may have poisoned some areas deeper in the stack, > > > > > * which we now need to unpoison. > > > > > diff --git a/include/linux/kasan.h b/include/linux/kasan.h > > > > > index 3f3f541e5d5f..7be9fb9146ac 100644 > > > > > --- a/include/linux/kasan.h > > > > > +++ b/include/linux/kasan.h > > > > > @@ -68,8 +68,6 @@ static inline void kasan_disable_current(void) {} > > > > > > > > > > void kasan_unpoison_memory(const void *address, size_t size); > > > > > > > > > > -void kasan_unpoison_task_stack(struct task_struct *task); > > > > > - > > > > > void kasan_alloc_pages(struct page *page, unsigned int order); > > > > > void kasan_free_pages(struct page *page, unsigned int order); > > > > > > > > > > @@ -114,8 +112,6 @@ void kasan_restore_multi_shot(bool enabled); > > > > > > > > > > static inline void kasan_unpoison_memory(const void *address, size_t size) {} > > > > > > > > > > -static inline void kasan_unpoison_task_stack(struct task_struct *task) {} > > > > > - > > > > > static inline void kasan_alloc_pages(struct page *page, unsigned int order) {} > > > > > static inline void kasan_free_pages(struct page *page, unsigned int order) {} > > > > > > > > > > @@ -167,6 +163,12 @@ static inline size_t kasan_metadata_size(struct kmem_cache *cache) { return 0; } > > > > > > > > > > #endif /* CONFIG_KASAN */ > > > > > > > > > > +#if defined(CONFIG_KASAN) && CONFIG_KASAN_STACK > > > > > > > > && defined(CONFIG_KASAN_STACK) for consistency > > > > > > CONFIG_KASAN_STACK is different from other KASAN configs. It's always > > > defined, and its value is what controls whether stack instrumentation > > > is enabled. > > > > Not sure why we did this instead of the following, but okay. > > > > config KASAN_STACK > > - int > > - default 1 if KASAN_STACK_ENABLE || CC_IS_GCC > > - default 0 > > + bool > > + default y if KASAN_STACK_ENABLE || CC_IS_GCC > > + default n > > I wondered the same, but then looking at scripts/Makefile.kasan I > think it's because we directly pass it to the compiler: > ... > $(call cc-param,asan-stack=$(CONFIG_KASAN_STACK)) \ > ... Try this instead: $(call cc-param,asan-stack=$(if $(CONFIG_KASAN_STACK),1,0)) \ -- Catalin