All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sergio González Collado" <sergio.collado@gmail.com>
To: stable@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
	"Sergio González Collado" <sergio.collado@gmail.com>
Subject: [PATCH 6.12.y 0/2] Kunit to check the longest symbol length
Date: Sun,  8 Jun 2025 16:54:48 +0200	[thread overview]
Message-ID: <20250608145450.7024-1-sergio.collado@gmail.com> (raw)

The longest length of a symbol (KSYM_NAME_LEN) was increased to 512 in
the reference [1]. Because in Rust symbols can become quite long due to
namespacing introduced by modules, types, traits, generics, etc.

This patch series presents two commits that implement a test to verify
that a symbol with KSYM_NAME_LEN of 512 can be read.

The first commit: To check that symbol length was valid, the commit
implements a kunit test that verifies that a symbol of 512 length can
be read.

The second commit: There was a warning when building with clang because
there was a definition of unlikely from compiler.h in tools/include/linux,
which conflicted with the one in the instruction decoder selftest.

[1] https://lore.kernel.org/lkml/20220802015052.10452-6-ojeda@kernel.org/

---
Nathan Chancellor (1):
  x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c

Sergio González Collado (1):
  Kunit to check the longest symbol length

 arch/x86/tools/insn_decoder_test.c |  5 +-
 lib/Kconfig.debug                  |  9 ++++
 lib/Makefile                       |  2 +
 lib/longest_symbol_kunit.c         | 82 ++++++++++++++++++++++++++++++
 4 files changed, 95 insertions(+), 3 deletions(-)
 create mode 100644 lib/longest_symbol_kunit.c


base-commit: ba9210b8c96355a16b78e1b890dce78f284d6f31
-- 
2.39.2


             reply	other threads:[~2025-06-08 14:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-08 14:54 Sergio González Collado [this message]
2025-06-08 14:54 ` [PATCH 6.12.y 1/2] Kunit to check the longest symbol length Sergio González Collado
2025-06-08 15:59   ` Miguel Ojeda
2025-06-08 16:10     ` Sergio González Collado
2025-06-17 14:00       ` Greg KH
2025-06-17 15:50         ` Sergio González Collado
2025-06-17 16:04           ` Miguel Ojeda
2025-06-09  2:34   ` Sasha Levin
2025-06-08 14:54 ` [PATCH 6.12.y 2/2] x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c Sergio González Collado
2025-06-08 16:00   ` Miguel Ojeda
2025-06-09  2:34   ` Sasha Levin
2025-06-08 15:59 ` [PATCH 6.12.y 0/2] Kunit to check the longest symbol length Miguel Ojeda

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=20250608145450.7024-1-sergio.collado@gmail.com \
    --to=sergio.collado@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ojeda@kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@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 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.