From: Kees Cook <keescook@chromium.org>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: Kees Cook <kees@kernel.org>,
akpm@linux-foundation.org, elver@google.com,
kasan-dev@googlegroups.com, davidgow@google.com, Jason@zx2c4.com,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] lib: fortify_kunit: build without structleak plugin
Date: Thu, 1 Dec 2022 09:07:28 -0800 [thread overview]
Message-ID: <202212010906.0CE64E9CD@keescook> (raw)
In-Reply-To: <CADYN=9LT7xWScSiprwgB2DhTN-Mws7rxG33BRZwLktK7P_jzkQ@mail.gmail.com>
On Mon, Nov 28, 2022 at 03:20:13PM +0100, Anders Roxell wrote:
> On Mon, 28 Nov 2022 at 15:09, Kees Cook <kees@kernel.org> wrote:
> >
> > On November 28, 2022 2:44:03 AM PST, Anders Roxell <anders.roxell@linaro.org> wrote:
> > >Building fortify_kunit with strucleak plugin enabled makes the stack
> > >frame size to grow.
> > >
> > >lib/fortify_kunit.c:140:1: error: the frame size of 2368 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
(It seems like lkml never got this email? Or at least I didn't find it
on lore, so "b4" was unhappy...)
> > Under what config
>
> I saw this with a arm64 allmodconfig build [1],
>
> > and compiler version do you see these warnings?
>
> Toolchain
> aarch64-linux-gnu-gcc (Debian 11.3.0-6) 11.3.0
Thanks! I've applied this to my tree.
--
Kees Cook
prev parent reply other threads:[~2022-12-01 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221128104403.2660703-1-anders.roxell@linaro.org>
[not found] ` <5FC4A1FD-9631-43B2-AE93-EFC059F892D3@kernel.org>
2022-11-28 14:20 ` [PATCH 2/2] lib: fortify_kunit: build without structleak plugin Anders Roxell
2022-12-01 17:07 ` Kees Cook [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=202212010906.0CE64E9CD@keescook \
--to=keescook@chromium.org \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=davidgow@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.