Received: by 10.192.165.148 with SMTP id m20csp1117879imm; Wed, 2 May 2018 14:32:10 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoQRht+Qz6DyF+1ebohdcNbDe9AH0dpt/UK7nbUT8Qznha1ixkAI6zrDfzr8vHt3Jg1Cr9S X-Received: by 2002:a63:942:: with SMTP id 63-v6mr17571792pgj.103.1525296730233; Wed, 02 May 2018 14:32:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525296730; cv=none; d=google.com; s=arc-20160816; b=FwWx5u5695/7LMrx0CeovcRfAgCnXHaG4e0nfyRJmXMSpzXtxcYb88KLCeeVB3ognu XV0Ync8PRRBee3U6xBNkcihRirC52BE3webqSAFQSEhJQpCpswY7E/6HH9iJv2jxAadt N+4aYukbNUwNaFvLd895r/mpuJkYLYQ3TaZlFqFujneM5xJ8HuQC4wBb1G91r4gX8Ltu Rr/Zpp1GUxTtRrpZwpsKJBBjfl/+GL8R+V3vY5TjWrF6OPbPwACRppDAhA6QezyfbC03 JIoDmB9gP5NA3G6ohpkg8tNbUyEb1tMOobbyHLr9ftkAUMZa1cSGRfHkO3XC92ysdJpL Ew0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=pBiMC04p2cYaU+0IqLOX4SQzzT3DW0nkRJzWwBuyY8U=; b=LJcChIse3yf/4g1vd3icPXTwfORmXmS6RV2rzlXjJ0scUEtXt2zw2F5cuRSOmDe4aD ifydQtWS5CEdxGizfAckH73W2w4moL7FeMPAvauwMCOu88Jqe7mR6pvIPJ6LDR30TyZd 2cL/QU41D8EOytfLOFS+qVAgbRjWOxh8BnqUXWMZcIk29L9IoNbCwK6VZihFdnY6oRc7 5KHfdNs6VKRWgj9tgBElSyzXurioGhGShN2TArB1+1qO/MibVkcQYYanaXoCBdak3fwH 10jyRrtd4crlWIPIileqCZ1FRCuwGDTefHkKWITnADe/jdoOJHuAyElfjc8sAVl2KIZB IbXQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@google.com header.s=20161025 header.b=gQVGtbyk; dkim=fail header.i=@chromium.org header.s=google header.b=AwTlP+fL; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t6si12443315pfg.114.2018.05.02.14.31.51; Wed, 02 May 2018 14:32:10 -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; dkim=fail header.i=@google.com header.s=20161025 header.b=gQVGtbyk; dkim=fail header.i=@chromium.org header.s=google header.b=AwTlP+fL; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751610AbeEBVb0 (ORCPT + 99 others); Wed, 2 May 2018 17:31:26 -0400 Received: from mail-ua0-f194.google.com ([209.85.217.194]:34721 "EHLO mail-ua0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750970AbeEBVbT (ORCPT ); Wed, 2 May 2018 17:31:19 -0400 Received: by mail-ua0-f194.google.com with SMTP id f22so10490288uam.1 for ; Wed, 02 May 2018 14:31:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=pBiMC04p2cYaU+0IqLOX4SQzzT3DW0nkRJzWwBuyY8U=; b=gQVGtbykGF6oZzv+D/dG9guPgjoOl8yrVSLfwfpYkTO+pfVBbnBKfbkqn6gSXG/rEd TQeS79m2Z/n4gx3cxBGcUqno92fpQVGFvIg/ELH9XaRpac+hZFMRpJIwfNLtDTTTs+ob hbHjgpxukL5uQm4UOuoxixjJwxrsyA9GD5/1JHfv2ZF2FL+HLHbxIM/lUXQFFkoPESef b+iKI2QH30pZDD/e+Iir7ZGI0JFx4KJcUGXyu5QeV3PJmqbswcYY9aLLCbw5qVWbhtVC mL4eELfuZg6kGA7FtyjNe3qdV77jEZQpzAgcQxXW46kCKHJSqvdKgdga0saqPQxqc0yp PSvw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=pBiMC04p2cYaU+0IqLOX4SQzzT3DW0nkRJzWwBuyY8U=; b=AwTlP+fL6in4BsJVL0oxD0F81jzgwlDbsOGwRLI1WtZiioO8mv8eeFbaow/+GPKaM1 oU8znH6ocO7QHXMc0PaambTUb/9NwinfIOMEGOjlLRnKNkaOVya2jRR8kTchLwT/y90o H3uG4rdfXSXxX4P5YHyD2kNRDrKwD87hIC8BU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=pBiMC04p2cYaU+0IqLOX4SQzzT3DW0nkRJzWwBuyY8U=; b=UII23Xr3eq8+JrIBurpNM5r3x9kbI53wbvCFXbgrXiFZNnIffoBdJ9RHrkltUNzJAt 34h+Y6j75M3Aq9+6T0lM1xf12wbRZ+swB6TXBD6pEansZPnuj6pAyQMscVSBQ86GcB7r Hbh478jWryR+3lQoGwX41F5M59s++R43EI9W3Pw0kM0M+Z0Sl5nxxeGhtwZWwgSQP9gE iVuZeh7oITFAJK5PO1YP5RjGlJiGROn7iRdqLVtEvS6W8qNlZ2KJK+be6GKkGZ/eQqnN yu8Wa93hq2XqbFifyyfSXD1rFGF1/GJLdT0W/dIq9oS6rHdfyIciAJRGBxCBqhb+y96C aAig== X-Gm-Message-State: ALQs6tAsfDXB9RfNc5L6MSAeC+8wnpLcM/W2Zj/LuG7KNfDUaantc2GR 1yMjbfO3WrJSdubuZnM07Llfh384hGXSK9sK7HhPRg== X-Received: by 10.159.59.213 with SMTP id y21mr19925102uah.167.1525296677621; Wed, 02 May 2018 14:31:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.11.209 with HTTP; Wed, 2 May 2018 14:31:16 -0700 (PDT) In-Reply-To: <20180502203326.9491-3-labbott@redhat.com> References: <20180502203326.9491-1-labbott@redhat.com> <20180502203326.9491-3-labbott@redhat.com> From: Kees Cook Date: Wed, 2 May 2018 14:31:16 -0700 X-Google-Sender-Auth: gxOoiHBonHFXkTN62GcLzshS03I Message-ID: Subject: Re: [PATCH 2/2] arm64: Clear the stack To: Laura Abbott Cc: Alexander Popov , Mark Rutland , Ard Biesheuvel , Kernel Hardening , linux-arm-kernel , LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 2, 2018 at 1:33 PM, Laura Abbott wrote: > > Implementation of stackleak based heavily on the x86 version Awesome! Notes below for both you and Alexander, since I think we can create a common code base instead of having near-duplicates in the arch/ trees... > > Signed-off-by: Laura Abbott > --- > Now written in C instead of a bunch of assembly. > --- > arch/arm64/Kconfig | 1 + > arch/arm64/include/asm/processor.h | 6 ++++ > arch/arm64/kernel/Makefile | 3 ++ > arch/arm64/kernel/entry.S | 6 ++++ > arch/arm64/kernel/erase.c | 55 +++++++++++++++++++++++++++++++++++ > arch/arm64/kernel/process.c | 16 ++++++++++ > drivers/firmware/efi/libstub/Makefile | 3 +- > scripts/Makefile.gcc-plugins | 5 +++- > 8 files changed, 93 insertions(+), 2 deletions(-) > create mode 100644 arch/arm64/kernel/erase.c > > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig > index eb2cf4938f6d..b0221db95dc9 100644 > --- a/arch/arm64/Kconfig > +++ b/arch/arm64/Kconfig > @@ -92,6 +92,7 @@ config ARM64 > select HAVE_ARCH_MMAP_RND_BITS > select HAVE_ARCH_MMAP_RND_COMPAT_BITS if COMPAT > select HAVE_ARCH_SECCOMP_FILTER > + select HAVE_ARCH_STACKLEAK > select HAVE_ARCH_THREAD_STRUCT_WHITELIST > select HAVE_ARCH_TRACEHOOK > select HAVE_ARCH_TRANSPARENT_HUGEPAGE > diff --git a/arch/arm64/include/asm/processor.h b/arch/arm64/include/asm/processor.h > index 767598932549..d31ab80ff647 100644 > --- a/arch/arm64/include/asm/processor.h > +++ b/arch/arm64/include/asm/processor.h > @@ -124,6 +124,12 @@ struct thread_struct { > unsigned long fault_address; /* fault info */ > unsigned long fault_code; /* ESR_EL1 value */ > struct debug_info debug; /* debugging */ > +#ifdef CONFIG_GCC_PLUGIN_STACKLEAK > + unsigned long lowest_stack; > +#ifdef CONFIG_STACKLEAK_METRICS > + unsigned long prev_lowest_stack; > +#endif > +#endif I wonder if x86 and arm64 could include a common struct here that was empty when the plugin is disabled... it would keep the ifdefs in one place. Maybe include/linux/stackleak.h could be: ---start--- /* Poison value points to the unused hole in the virtual memory map */ #define STACKLEAK_POISON -0xBEEF #define STACKLEAK_POISON_CHECK_DEPTH 128 struct stackleak { #ifdef CONFIG_GCC_PLUGIN_STACKLEAK unsigned long lowest; #ifdef CONFIG_STACKLEAK_METRICS unsigned long prev_lowest; #endif #endif }; asmlinkage void erase_kstack(void); ---eof--- and arch/*/include/asm/processor.h could do: @@ -124,6 +124,12 @@ struct thread_struct { unsigned long fault_address; /* fault info */ unsigned long fault_code; /* ESR_EL1 value */ struct debug_info debug; /* debugging */ + struct stackleak stackleak; and arch/x86/entry/erase.c could move to maybe kernel/stackleak.c? (Oh, I notice this needs an SPDX line too.) > static inline void arch_thread_struct_whitelist(unsigned long *offset, > diff --git a/arch/arm64/kernel/Makefile b/arch/arm64/kernel/Makefile > index bf825f38d206..0ceea613c65b 100644 > --- a/arch/arm64/kernel/Makefile > +++ b/arch/arm64/kernel/Makefile > @@ -55,6 +55,9 @@ arm64-reloc-test-y := reloc_test_core.o reloc_test_syms.o > arm64-obj-$(CONFIG_CRASH_DUMP) += crash_dump.o > arm64-obj-$(CONFIG_ARM_SDE_INTERFACE) += sdei.o > > +arm64-obj-$(CONFIG_GCC_PLUGIN_STACKLEAK) += erase.o > +KASAN_SANITIZE_erase.o := n > + > obj-y += $(arm64-obj-y) vdso/ probes/ > obj-m += $(arm64-obj-m) > head-y := head.o > diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S > index ec2ee720e33e..3144f1ebdc18 100644 > --- a/arch/arm64/kernel/entry.S > +++ b/arch/arm64/kernel/entry.S > @@ -401,6 +401,11 @@ tsk .req x28 // current thread_info > > .text > > + .macro ERASE_KSTACK > +#ifdef CONFIG_GCC_PLUGIN_STACKLEAK > + bl erase_kstack > +#endif > + .endm > /* > * Exception vectors. > */ > @@ -906,6 +911,7 @@ ret_to_user: > cbnz x2, work_pending > finish_ret_to_user: > enable_step_tsk x1, x2 > + ERASE_KSTACK > kernel_exit 0 > ENDPROC(ret_to_user) Nice. All of the return paths end up here (I went looking for ret_from_fork's path). :) > > diff --git a/arch/arm64/kernel/erase.c b/arch/arm64/kernel/erase.c > new file mode 100644 > index 000000000000..b8b5648d893b > --- /dev/null > +++ b/arch/arm64/kernel/erase.c > @@ -0,0 +1,55 @@ > +#include > +#include > +#include > +#include > +#include > + > +asmlinkage void erase_kstack(void) > +{ > + unsigned long p = current->thread.lowest_stack; > + unsigned long boundary = p & ~(THREAD_SIZE - 1); > + unsigned long poison = 0; > + const unsigned long check_depth = STACKLEAK_POISON_CHECK_DEPTH / > + sizeof(unsigned long); > + > + /* > + * Let's search for the poison value in the stack. > + * Start from the lowest_stack and go to the bottom. > + */ > + while (p > boundary && poison <= check_depth) { > + if (*(unsigned long *)p == STACKLEAK_POISON) > + poison++; > + else > + poison = 0; > + > + p -= sizeof(unsigned long); > + } > + > + /* > + * One long int at the bottom of the thread stack is reserved and > + * should not be poisoned (see CONFIG_SCHED_STACK_END_CHECK). > + */ > + if (p == boundary) > + p += sizeof(unsigned long); > + > +#ifdef CONFIG_STACKLEAK_METRICS > + current->thread.prev_lowest_stack = p; > +#endif > + > + /* > + * So let's write the poison value to the kernel stack. > + * Start from the address in p and move up till the new boundary. > + */ > + boundary = current_stack_pointer; This is the only difference between x86 and arm64 in this code. What do you think about implementing on_thread_stack() to match x86: if (on_thread_stack()) boundary = current_stack_pointer; else boundary = current_top_of_stack(); then we could make this common code too instead of having two copies in arch/? > + BUG_ON(boundary - p >= THREAD_SIZE); > + > + while (p < boundary) { > + *(unsigned long *)p = STACKLEAK_POISON; > + p += sizeof(unsigned long); > + } > + > + /* Reset the lowest_stack value for the next syscall */ > + current->thread.lowest_stack = current_stack_pointer; > +} > + > diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c > index f08a2ed9db0d..156fa0a0da19 100644 > --- a/arch/arm64/kernel/process.c > +++ b/arch/arm64/kernel/process.c > @@ -364,6 +364,9 @@ int copy_thread(unsigned long clone_flags, unsigned long stack_start, > p->thread.cpu_context.pc = (unsigned long)ret_from_fork; > p->thread.cpu_context.sp = (unsigned long)childregs; > > +#ifdef CONFIG_GCC_PLUGIN_STACKLEAK > + p->thread.lowest_stack = (unsigned long)task_stack_page(p); > +#endif > ptrace_hw_copy_thread(p); > > return 0; > @@ -493,3 +496,16 @@ void arch_setup_new_exec(void) > { > current->mm->context.flags = is_compat_task() ? MMCF_AARCH32 : 0; > } > + > +#ifdef CONFIG_GCC_PLUGIN_STACKLEAK > +void __used check_alloca(unsigned long size) > +{ > + unsigned long sp, stack_left; > + > + sp = current_stack_pointer; > + > + stack_left = sp & (THREAD_SIZE - 1); > + BUG_ON(stack_left < 256 || size >= stack_left - 256); > +} > +EXPORT_SYMBOL(check_alloca); This is pretty different from x86. Is this just an artifact of ORC, or something else? > +#endif > diff --git a/drivers/firmware/efi/libstub/Makefile b/drivers/firmware/efi/libstub/Makefile > index a34e9290a699..25dd2a14560d 100644 > --- a/drivers/firmware/efi/libstub/Makefile > +++ b/drivers/firmware/efi/libstub/Makefile > @@ -20,7 +20,8 @@ cflags-$(CONFIG_EFI_ARMSTUB) += -I$(srctree)/scripts/dtc/libfdt > KBUILD_CFLAGS := $(cflags-y) -DDISABLE_BRANCH_PROFILING \ > -D__NO_FORTIFY \ > $(call cc-option,-ffreestanding) \ > - $(call cc-option,-fno-stack-protector) > + $(call cc-option,-fno-stack-protector) \ > + $(DISABLE_STACKLEAK_PLUGIN) > > GCOV_PROFILE := n > KASAN_SANITIZE := n > diff --git a/scripts/Makefile.gcc-plugins b/scripts/Makefile.gcc-plugins > index 8d6070fc538f..6cc0e35d3324 100644 > --- a/scripts/Makefile.gcc-plugins > +++ b/scripts/Makefile.gcc-plugins > @@ -37,11 +37,14 @@ ifdef CONFIG_GCC_PLUGINS > > gcc-plugin-$(CONFIG_GCC_PLUGIN_STACKLEAK) += stackleak_plugin.so > gcc-plugin-cflags-$(CONFIG_GCC_PLUGIN_STACKLEAK) += -DSTACKLEAK_PLUGIN -fplugin-arg-stackleak_plugin-track-min-size=$(CONFIG_STACKLEAK_TRACK_MIN_SIZE) > + ifdef CONFIG_GCC_PLUGIN_STACKLEAK > + DISABLE_STACKLEAK_PLUGIN += -fplugin-arg-stackleak_plugin-disable > + endif > > GCC_PLUGINS_CFLAGS := $(strip $(addprefix -fplugin=$(objtree)/scripts/gcc-plugins/, $(gcc-plugin-y)) $(gcc-plugin-cflags-y)) > > export PLUGINCC GCC_PLUGINS_CFLAGS GCC_PLUGIN GCC_PLUGIN_SUBDIR > - export SANCOV_PLUGIN DISABLE_LATENT_ENTROPY_PLUGIN > + export SANCOV_PLUGIN DISABLE_LATENT_ENTROPY_PLUGIN DISABLE_STACKLEAK_PLUGIN > > ifneq ($(PLUGINCC),) > # SANCOV_PLUGIN can be only in CFLAGS_KCOV because avoid duplication. > -- > 2.14.3 > -Kees -- Kees Cook Pixel Security