From: Nathan Chancellor <nathan@kernel.org>
To: "Sergio González Collado" <sergio.collado@gmail.com>
Cc: David Gow <davidgow@google.com>, Rae Moar <rmoar@google.com>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
Miguel Ojeda <ojeda@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
rust-for-linux@vger.kernel.org,
Josh Poimboeuf <jpoimboe@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
David Laight <david.laight.linux@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Martin Rodriguez Reboredo <yakoyoku@gmail.com>,
x86@kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] kunit: fix longest symbol length test
Date: Sun, 27 Apr 2025 16:09:16 -0400 [thread overview]
Message-ID: <20250427200916.GA1661412@ax162> (raw)
In-Reply-To: <20250427191009.6179-1-sergio.collado@gmail.com>
Hi Sergio,
On Sun, Apr 27, 2025 at 09:10:09PM +0200, Sergio González Collado wrote:
> The kunit test that checks the longests symbol length [1], has triggered
> warnings in some CI pilelines when symbol prefixes are used [2]. The test
> is adjusted to depend on !CONFIG_PREFIX_SYMBOLS as sujested in [3].
>
> [1] https://lore.kernel.org/rust-for-linux/CABVgOSm=5Q0fM6neBhxSbOUHBgNzmwf2V22vsYC10YRBT=kN1g@mail.gmail.com/T/#t
> [2] https://lore.kernel.org/all/20250328112156.2614513-1-arnd@kernel.org/T/#u
> [3] https://lore.kernel.org/all/ycgbf7jcq7nc62ndqiynogt6hkabgl3hld4uyelgo7rksylf32@oysq7jpchtp4/
>
> Fixes: c104c16073b7 ("Kunit to check the longest symbol length")
> Signed-off-by: Sergio González Collado <sergio.collado@gmail.com>
> ---
> lib/Kconfig.debug | 2 +-
> lib/tests/longest_symbol_kunit.c | 3 +--
> 2 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index f9051ab610d5..6937dedce04d 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -2885,7 +2885,7 @@ config FORTIFY_KUNIT_TEST
>
> config LONGEST_SYM_KUNIT_TEST
> tristate "Test the longest symbol possible" if !KUNIT_ALL_TESTS
> - depends on KUNIT && KPROBES
> + depends on KUNIT && KPROBES && !CONFIG_PREFIX_SYMBOLS
This should be !PREFIX_SYMBOLS, otherwise it would be looking for a
CONFIG_CONFIG_PREFIX_SYMBOLS not to exist, which will always be true.
This solution does not appear to take into account Peter's comment
around how kCFI will prefix these symbols as well? Should it depend on
!CFI_CLANG as well?
https://lore.kernel.org/20250411065054.GM9833@noisy.programming.kicks-ass.net/
> default KUNIT_ALL_TESTS
> help
> Tests the longest symbol possible
> diff --git a/lib/tests/longest_symbol_kunit.c b/lib/tests/longest_symbol_kunit.c
> index e3c28ff1807f..b183fb92d1b2 100644
> --- a/lib/tests/longest_symbol_kunit.c
> +++ b/lib/tests/longest_symbol_kunit.c
> @@ -3,8 +3,7 @@
> * Test the longest symbol length. Execute with:
> * ./tools/testing/kunit/kunit.py run longest-symbol
> * --arch=x86_64 --kconfig_add CONFIG_KPROBES=y --kconfig_add CONFIG_MODULES=y
> - * --kconfig_add CONFIG_RETPOLINE=n --kconfig_add CONFIG_CFI_CLANG=n
> - * --kconfig_add CONFIG_MITIGATION_RETPOLINE=n
> + * --kconfig_add CONFIG_CPU_MITIGATIONS=n
> */
>
> #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
>
> base-commit: f1a3944c860b0615d0513110d8cf62bb94adbb41
> --
> 2.39.2
>
prev parent reply other threads:[~2025-04-27 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 19:10 [PATCH] kunit: fix longest symbol length test Sergio González Collado
2025-04-27 20:09 ` Nathan Chancellor [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=20250427200916.GA1661412@ax162 \
--to=nathan@kernel.org \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=david.laight.linux@gmail.com \
--cc=davidgow@google.com \
--cc=jpoimboe@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rmoar@google.com \
--cc=rostedt@goodmis.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sergio.collado@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=x86@kernel.org \
--cc=yakoyoku@gmail.com \
/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