linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Ryabinin <ryabinin.a.a@gmail.com>
To: Will Deacon <will.deacon@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: Matt Fleming <matt.fleming@intel.com>,
	linux-efi@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Alexander Potapenko <glider@google.com>,
	Dmitry Vyukov <dvyukov@google.com>, Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org,
	Andrey Ryabinin <ryabinin.a.a@gmail.com>
Subject: [PATCH 2/4] efi/runtime-wrappers, kasan: don't sanitize runtime wrappers.
Date: Wed, 26 Aug 2015 19:15:05 +0300	[thread overview]
Message-ID: <1440605707-8325-3-git-send-email-ryabinin.a.a@gmail.com> (raw)
In-Reply-To: <1440605707-8325-1-git-send-email-ryabinin.a.a@gmail.com>

ARM64 maps efi runtime services in userspace addresses
which don't have KASAN shadow. So dereferencing these addresses
in efi_call_virt() will cause crash if this code instrumented.

Signed-off-by: Andrey Ryabinin <ryabinin.a.a@gmail.com>
---
 drivers/firmware/efi/Makefile | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/drivers/firmware/efi/Makefile b/drivers/firmware/efi/Makefile
index 6fd3da9..413fcf2 100644
--- a/drivers/firmware/efi/Makefile
+++ b/drivers/firmware/efi/Makefile
@@ -1,6 +1,14 @@
 #
 # Makefile for linux kernel
 #
+
+#
+# ARM64 maps efi runtime services in userspace addresses
+# which don't have KASAN shadow. So dereference of these addresses
+# in efi_call_virt() will cause crash if this code instrumented.
+#
+KASAN_SANITIZE_runtime-wrappers.o	:= n
+
 obj-$(CONFIG_EFI)			+= efi.o vars.o reboot.o
 obj-$(CONFIG_EFI_VARS)			+= efivars.o
 obj-$(CONFIG_EFI_ESRT)			+= esrt.o
-- 
2.4.6

  parent reply	other threads:[~2015-08-26 16:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 16:15 [PATCH 0/4] KASAN/ARM64 EFI fixes Andrey Ryabinin
2015-08-26 16:15 ` [PATCH 1/4] x86, efi, kasan: #undef memset/memcpy/memmove per arch Andrey Ryabinin
2015-08-28  6:27   ` Ingo Molnar
     [not found]     ` <20150828062745.GB1928-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-08-28  8:39       ` Leif Lindholm
     [not found]         ` <20150828083941.GN10728-t77nlHhSwNqAroYi2ySoxKxOck334EZe@public.gmane.org>
2015-08-28  9:53           ` Ingo Molnar
2015-08-28 11:09       ` [PATCH v2] " Andrey Ryabinin
     [not found]         ` <1440760199-18111-1-git-send-email-ryabinin.a.a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-08-28 14:43           ` Matt Fleming
     [not found]             ` <20150828144358.GI2759-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-08-28 14:57               ` Andrey Ryabinin
2015-08-26 16:15 ` Andrey Ryabinin [this message]
     [not found] ` <1440605707-8325-1-git-send-email-ryabinin.a.a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-08-26 16:15   ` [PATCH 3/4] arm64/efi-stub, kasan: don't instrument efi-stub Andrey Ryabinin
2015-08-26 16:15 ` [PATCH 4/4] libfdt, kasan: don't instrument libfdt Andrey Ryabinin

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=1440605707-8325-3-git-send-email-ryabinin.a.a@gmail.com \
    --to=ryabinin.a.a@gmail.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).