From: Arnd Bergmann <a...@arndb.de>
I ran into a couple of problems with kunit tests taking too much stack
space, sometimes dangerously so. These the the three instances that
cause an increase over the warning limit of some architectures:
lib/bitfield_kunit.c:93:1: error: the frame size of 7440 bytes is larger than
2048 bytes [-Werror=frame-larger-than=]
drivers/base/test/property-entry-test.c:481:1: error: the frame size of 2640
bytes is larger than 2048 bytes [-Werror=frame-larger-than=]
drivers/thunderbolt/test.c:1529:1: error: the frame size of 1176 bytes is
larger than 1024 bytes [-Werror=frame-larger-than=]
Ideally there should be a way to rewrite the kunit infrastructure
that avoids the explosion of stack data when the structleak plugin
is used.
A rather drastic measure would be to use Kconfig logic to make
the two options mutually exclusive. This would clearly work, but
is probably not needed.
As a simpler workaround, this disables the plugin for the three
files in which the excessive stack usage was observed.
Arnd
Arnd Bergmann (3):
bitfield: build kunit tests without structleak plugin
drivers/base: build kunit tests without structleak plugin
thunderbolt: build kunit tests without structleak plugin
drivers/base/test/Makefile | 1 +
drivers/thunderbolt/Makefile | 1 +
lib/Makefile | 1 +
3 files changed, 3 insertions(+)
Cc: Kees Cook <keesc...@chromium.org>
Cc: Brendan Higgins <brendanhigg...@google.com>
Cc: Shuah Khan <sk...@linuxfoundation.org>
Cc: Geert Uytterhoeven <geert+rene...@glider.be>
Cc: Alan Maguire <alan.magu...@oracle.com>
Cc: Dmitry Torokhov <dmitry.torok...@gmail.com>
Cc: Mika Westerberg <mika.westerb...@linux.intel.com>
Cc: Vitor Massaru Iha <vi...@massaru.org>
Cc: linux-harden...@vger.kernel.org
Cc: linux-kselft...@vger.kernel.org
Cc: kunit-...@googlegroups.com
Cc: linux-kernel@vger.kernel.org
--
2.29.2
