From: Nathan Chancellor <natechancellor@gmail.com>
To: Marco Elver <elver@google.com>
Cc: Arnd Bergmann <arnd@kernel.org>,
Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
Nick Desaulniers <ndesaulniers@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
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:36 -0700 [thread overview]
Message-ID: <20210104223336.GA2562866@ubuntu-m3-large-x86> (raw)
In-Reply-To: <CANpmjNNGmbgg_pFMC6X_6vZcj53jy7PsNyZAC88rOQC5zrOiFw@mail.gmail.com>
On Wed, Dec 30, 2020 at 05:13:03PM +0100, Marco Elver wrote:
> On Wed, 30 Dec 2020 at 16:47, Arnd Bergmann <arnd@kernel.org> wrote:
> >
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > Building ubsan kernels even for compile-testing introduced these
> > warnings in my randconfig environment:
> >
> > crypto/blake2b_generic.c:98:13: error: stack frame size of 9636 bytes in function 'blake2b_compress' [-Werror,-Wframe-larger-than=]
> > static void blake2b_compress(struct blake2b_state *S,
> > crypto/sha512_generic.c:151:13: error: stack frame size of 1292 bytes in function 'sha512_generic_block_fn' [-Werror,-Wframe-larger-than=]
> > static void sha512_generic_block_fn(struct sha512_state *sst, u8 const *src,
> > lib/crypto/curve25519-fiat32.c:312:22: error: stack frame size of 2180 bytes in function 'fe_mul_impl' [-Werror,-Wframe-larger-than=]
> > static noinline void fe_mul_impl(u32 out[10], const u32 in1[10], const u32 in2[10])
> > lib/crypto/curve25519-fiat32.c:444:22: error: stack frame size of 1588 bytes in function 'fe_sqr_impl' [-Werror,-Wframe-larger-than=]
> > static noinline void fe_sqr_impl(u32 out[10], const u32 in1[10])
> >
> > Further testing showed that this is caused by
> > -fsanitize=unsigned-integer-overflow.
> >
> > The one in blake2b immediately overflows the 8KB stack area on 32-bit
> > architectures, so better ensure this never happens by making this
> > option gcc-only.
This patch also fixes the failed BUILD_BUG issue in mm/mremap.c that you
sent a patch for [1], along with a couple of other issues I see such as:
ld.lld: error: undefined symbol: __bad_mask
>>> referenced by gpi.c
>>> dma/qcom/gpi.o:(gpi_update_reg) in archive
>>> drivers/built-in.a
>>> referenced by gpi.c
>>> dma/qcom/gpi.o:(gpi_update_reg) in archive
>>> drivers/built-in.a
[1]: https://lore.kernel.org/lkml/20201230154104.522605-1-arnd@kernel.org/
Reviewed-by: Nathan Chancellor <natechancellor@gmail.com>
> > Fixes: d0a3ac549f38 ("ubsan: enable for all*config builds")
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > ---
> > lib/Kconfig.ubsan | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/lib/Kconfig.ubsan b/lib/Kconfig.ubsan
> > index 8b635fd75fe4..e23873282ba7 100644
> > --- a/lib/Kconfig.ubsan
> > +++ 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
> > + depends on !CC_IS_CLANG
> > depends on $(cc-option,-fsanitize=unsigned-integer-overflow)
> > help
> > This option enables -fsanitize=unsigned-integer-overflow which checks
> > --
> > 2.29.2
> >
next prev parent reply other threads:[~2021-01-04 23:37 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 [this message]
2021-01-04 23:33 ` Andrew Morton
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=20210104223336.GA2562866@ubuntu-m3-large-x86 \
--to=natechancellor@gmail.com \
--cc=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=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®