From: Andrew Morton <akpm@linux-foundation.org>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Marco Elver <elver@google.com>, Arnd Bergmann <arnd@kernel.org>,
Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
Nick Desaulniers <ndesaulniers@google.com>,
George Popescu <georgepope@android.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] ubsan: disable unsigned-integer-overflow sanitizer with clang
Date: Mon, 4 Jan 2021 15:33:33 -0800 [thread overview]
Message-ID: <20210104153333.4b6c7ae49edc4182d53bd17f@linux-foundation.org> (raw)
In-Reply-To: <20210104223336.GA2562866@ubuntu-m3-large-x86>
On Mon, 4 Jan 2021 15:33:36 -0700 Nathan Chancellor <natechancellor@gmail.com> wrote:
> > > +++ b/lib/Kconfig.ubsan
> > > @@ -122,6 +122,8 @@ config UBSAN_SIGNED_OVERFLOW
> > >
> > > config UBSAN_UNSIGNED_OVERFLOW
> > > bool "Perform checking for unsigned arithmetic overflow"
> > > + # clang hugely expands stack usage with -fsanitize=object-size
> >
> > This is the first time -fsanitize=object-size is mentioned. Typo?
>
> Copy and paste issue from CONFIG_UBSAN_OBJECT_SIZE
This?
--- a/lib/Kconfig.ubsan~ubsan-disable-unsigned-integer-overflow-sanitizer-with-clang-fix
+++ a/lib/Kconfig.ubsan
@@ -122,7 +122,7 @@ config UBSAN_SIGNED_OVERFLOW
config UBSAN_UNSIGNED_OVERFLOW
bool "Perform checking for unsigned arithmetic overflow"
- # clang hugely expands stack usage with -fsanitize=object-size
+ # clang hugely expands stack usage with -fsanitize=unsigned-integer-overflow
depends on !CC_IS_CLANG
depends on $(cc-option,-fsanitize=unsigned-integer-overflow)
help
_
next prev parent reply other threads:[~2021-01-04 23:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:47 Arnd Bergmann
2020-12-30 16:13 ` Marco Elver
2021-01-04 22:33 ` Nathan Chancellor
2021-01-04 23:33 ` Andrew Morton [this message]
2021-01-04 23:34 ` Nathan Chancellor
2021-01-05 9:25 ` Arnd Bergmann
2021-01-06 9:12 ` Arnd Bergmann
2021-01-06 21:38 ` Nathan Chancellor
2021-01-06 22:06 ` Arnd Bergmann
2021-01-07 3:34 ` Nathan Chancellor
2021-01-06 21:57 ` Kees Cook
2021-01-06 22:12 ` Arnd Bergmann
2021-01-06 23:17 ` Kees Cook
2021-01-06 23:40 ` Arnd Bergmann
2021-01-07 16:09 ` Arnd Bergmann
2021-01-07 17:22 ` Kees Cook
2021-01-07 18:15 ` Nathan Chancellor
2021-01-07 20:41 ` Arnd Bergmann
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=20210104153333.4b6c7ae49edc4182d53bd17f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=elver@google.com \
--cc=georgepope@android.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®