From: Brendan Higgins <brendanhiggins@google.com>
To: shuah@kernel.org, davidgow@google.com, arnd@arndb.de,
keescook@chromium.org, rafael@kernel.org, jic23@kernel.org,
lars@metafoo.de, ulf.hansson@linaro.org,
andreas.noever@gmail.com, michael.jamet@intel.com,
mika.westerberg@linux.intel.com, YehezkelShB@gmail.com,
masahiroy@kernel.org, michal.lkml@markovi.net,
ndesaulniers@google.com
Cc: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-usb@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-kbuild@vger.kernel.org,
Brendan Higgins <brendanhiggins@google.com>
Subject: [PATCH v2 5/5] bitfield: build kunit tests without structleak plugin
Date: Wed, 29 Sep 2021 14:27:13 -0700 [thread overview]
Message-ID: <20210929212713.1213476-6-brendanhiggins@google.com> (raw)
In-Reply-To: <20210929212713.1213476-1-brendanhiggins@google.com>
From: Arnd Bergmann <arnd@arndb.de>
The structleak plugin causes the stack frame size to grow immensely:
lib/bitfield_kunit.c: In function 'test_bitfields_constants':
lib/bitfield_kunit.c:93:1: error: the frame size of 7440 bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
Turn it off in this file.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
---
Changes since last revision:
- Dropped -Wframe-larger-than=10240 from CFLAGS.
---
lib/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/Makefile b/lib/Makefile
index 5efd1b435a37c..a841be5244ac6 100644
--- a/lib/Makefile
+++ b/lib/Makefile
@@ -351,7 +351,7 @@ obj-$(CONFIG_OBJAGG) += objagg.o
obj-$(CONFIG_PLDMFW) += pldmfw/
# KUnit tests
-CFLAGS_bitfield_kunit.o := $(call cc-option,-Wframe-larger-than=10240)
+CFLAGS_bitfield_kunit.o := $(DISABLE_STRUCTLEAK_PLUGIN)
obj-$(CONFIG_BITFIELD_KUNIT) += bitfield_kunit.o
obj-$(CONFIG_LIST_KUNIT_TEST) += list-test.o
obj-$(CONFIG_LINEAR_RANGES_TEST) += test_linear_ranges.o
--
2.33.0.685.g46640cef36-goog
prev parent reply other threads:[~2021-09-29 21:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 21:27 [PATCH v2 0/5] kunit: build kunit tests without structleak plugin Brendan Higgins
2021-09-29 21:27 ` [PATCH v2 1/5] gcc-plugins/structleak: add makefile var for disabling structleak Brendan Higgins
2021-09-30 0:12 ` David Gow
2021-09-29 21:27 ` [PATCH v2 2/5] iio/test-format: build kunit tests without structleak plugin Brendan Higgins
2021-09-29 21:27 ` [PATCH v2 3/5] device property: " Brendan Higgins
2021-09-29 21:27 ` [PATCH v2 4/5] thunderbolt: " Brendan Higgins
2021-09-29 21:27 ` Brendan Higgins [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=20210929212713.1213476-6-brendanhiggins@google.com \
--to=brendanhiggins@google.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=arnd@arndb.de \
--cc=davidgow@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=keescook@chromium.org \
--cc=kunit-dev@googlegroups.com \
--cc=lars@metafoo.de \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michael.jamet@intel.com \
--cc=michal.lkml@markovi.net \
--cc=mika.westerberg@linux.intel.com \
--cc=ndesaulniers@google.com \
--cc=rafael@kernel.org \
--cc=shuah@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ulf.hansson@linaro.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).