From: Changbin Du <changbin.du@gmail.com>
To: Changbin Du <changbin.du@gmail.com>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
hpa@zytor.com, x86@kernel.org, Andy Lutomirski <luto@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 0/2] Add SANITIZE_xx.o & SANITIZE and apply them to x86
Date: Wed, 12 Feb 2020 20:28:42 +0800 [thread overview]
Message-ID: <20200212122840.5p3kvijii3qboltt@mail.google.com> (raw)
In-Reply-To: <20200201062459.7150-1-changbin.du@gmail.com>
Hello, Any comments? Thanks.
On Sat, Feb 01, 2020 at 02:24:57PM +0800, Changbin Du wrote:
> These two patches add SANITIZE_xx.o and SANITIZE to disable all sanitizers for
> specific files, and apply them to x86 booting code.
>
> We need to disable UBSAN for some of ealy stage code:
> o For code which could operate in one-one mapping mode. In this case,
> kernel would crash at accessing data parameter when invoking UBSAN
> handlers.
> o Since UBSAN handlers are instrumented by KASAN, so invoking UBSAN
> handlers before KASAN is initiated also is not allowed.
>
> Changbin Du (2):
> sanitize: Add SANITIZE_xx.o and SANITIZE to disable all sanitizers for
> specific files
> x86: Disable both KASAN and UBSAN for some booting code
>
> Documentation/dev-tools/kasan.rst | 12 ++++++++++++
> arch/x86/boot/Makefile | 2 +-
> arch/x86/boot/compressed/Makefile | 2 +-
> arch/x86/entry/vdso/Makefile | 3 +--
> arch/x86/kernel/Makefile | 10 +++++-----
> arch/x86/lib/Makefile | 2 +-
> arch/x86/mm/Makefile | 4 ++--
> arch/x86/realmode/Makefile | 2 +-
> arch/x86/realmode/rm/Makefile | 2 +-
> scripts/Makefile.lib | 4 ++--
> 10 files changed, 27 insertions(+), 16 deletions(-)
>
> --
> 2.24.0
>
--
Cheers,
Changbin Du
prev parent reply other threads:[~2020-02-12 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 6:24 [PATCH 0/2] Add SANITIZE_xx.o & SANITIZE and apply them to x86 Changbin Du
2020-02-01 6:24 ` [PATCH 1/2] sanitize: Add SANITIZE_xx.o and SANITIZE to disable all sanitizers for specific files Changbin Du
2020-02-16 4:46 ` Masahiro Yamada
2020-02-01 6:24 ` [PATCH 2/2] x86: Disable both KASAN and UBSAN for some booting code Changbin Du
2020-02-12 12:28 ` Changbin Du [this message]
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=20200212122840.5p3kvijii3qboltt@mail.google.com \
--to=changbin.du@gmail.com \
--cc=aryabinin@virtuozzo.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).