From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Kees Cook <keescook@chromium.org>,
Brendan Higgins <brendanhiggins@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Alan Maguire <alan.maguire@oracle.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Vitor Massaru Iha <vitor@massaru.org>,
linux-hardening@vger.kernel.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com,
Andreas Noever <andreas.noever@gmail.com>,
linux-usb@vger.kernel.org
Subject: Re: [RFC 3/3] thunderbolt: build kunit tests without structleak plugin
Date: Wed, 27 Jan 2021 14:53:04 +0200 [thread overview]
Message-ID: <20210127125304.GD2542@lahna.fi.intel.com> (raw)
In-Reply-To: <20210125124533.101339-4-arnd@kernel.org>
Hi Arnd,
On Mon, Jan 25, 2021 at 01:45:28PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The structleak plugin causes the stack frame size to grow immensely:
>
> drivers/thunderbolt/test.c:1529:1: error: the frame size of 1176 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
>
> Turn it off in this file.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
To me this is a reasonable work around so I can pick this up to
Thunderbolt tree if no objections.
Thanks BTW, for doing this. I got a report from buildbot some time ago
about the this but did not have time to figure out how to fix it :)
next prev parent reply other threads:[~2021-01-27 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 12:45 [RFC 0/3] kunit vs structleak Arnd Bergmann
2021-01-25 12:45 ` [RFC 1/3] bitfield: build kunit tests without structleak plugin Arnd Bergmann
2021-01-25 12:45 ` [RFC 2/3] drivers/base: " Arnd Bergmann
2021-01-25 12:45 ` [RFC 3/3] thunderbolt: " Arnd Bergmann
2021-01-27 12:53 ` Mika Westerberg [this message]
2021-01-27 20:15 ` [RFC 0/3] kunit vs structleak Kees Cook
2021-01-29 21:29 ` Brendan Higgins
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=20210127125304.GD2542@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=alan.maguire@oracle.com \
--cc=andreas.noever@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=brendanhiggins@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=keescook@chromium.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vitor@massaru.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.