From: Marco Elver <elver@google.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, keescook@chromium.org,
davidgow@google.com, Jason@zx2c4.com,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/2] kernel: kcsan: kcsan_test: build without structleak plugin
Date: Mon, 28 Nov 2022 15:27:44 +0100 [thread overview]
Message-ID: <CANpmjNP8-jDPXJVy68zhkspEac8vutfpTAc1nytnyExSpsT-jA@mail.gmail.com> (raw)
In-Reply-To: <20221128104358.2660634-1-anders.roxell@linaro.org>
On Mon, 28 Nov 2022 at 11:44, Anders Roxell <anders.roxell@linaro.org> wrote:
>
> Building kcsan_test with strucleak plugin enabled makes the stack frame
> size to grow.
>
> kernel/kcsan/kcsan_test.c:704:1: error: the frame size of 3296 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
>
> Turn off the structleak plugin checks for kcsan_test.
>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
Acked-by: Marco Elver <elver@google.com>
> ---
> kernel/kcsan/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/kcsan/Makefile b/kernel/kcsan/Makefile
> index 4f35d1bced6a..8cf70f068d92 100644
> --- a/kernel/kcsan/Makefile
> +++ b/kernel/kcsan/Makefile
> @@ -17,4 +17,5 @@ KCSAN_INSTRUMENT_BARRIERS_selftest.o := y
> obj-$(CONFIG_KCSAN_SELFTEST) += selftest.o
>
> CFLAGS_kcsan_test.o := $(CFLAGS_KCSAN) -g -fno-omit-frame-pointer
> +CFLAGS_kcsan_test.o += $(DISABLE_STRUCTLEAK_PLUGIN)
> obj-$(CONFIG_KCSAN_KUNIT_TEST) += kcsan_test.o
> --
> 2.35.1
>
prev parent reply other threads:[~2022-11-28 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 10:43 [PATCH 1/2] kernel: kcsan: kcsan_test: build without structleak plugin Anders Roxell
2022-11-28 14:27 ` Marco Elver [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=CANpmjNP8-jDPXJVy68zhkspEac8vutfpTAc1nytnyExSpsT-jA@mail.gmail.com \
--to=elver@google.com \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=davidgow@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.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 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).