From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, sergio.collado@gmail.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v2 6.1.y 1/2] Kunit to check the longest symbol length
Date: Wed, 25 Jun 2025 10:07:09 -0400 [thread overview]
Message-ID: <20250624212005-4e6f8fdd63735ebb@stable.kernel.org> (raw)
In-Reply-To: <20250624165852.7689-2-sergio.collado@gmail.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
⚠️ Found follow-up fixes in mainline
The upstream commit SHA1 provided is correct: c104c16073b7fdb3e4eae18f66f4009f6b073d6f
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 27f827e7cc03)
6.6.y | Not found
Found fixes commits:
f710202b2a45 x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c
Note: The patch differs from the upstream commit:
---
1: c104c16073b7f ! 1: bd506eb0975a0 Kunit to check the longest symbol length
@@ Metadata
## Commit message ##
Kunit to check the longest symbol length
+ commit c104c16073b7fdb3e4eae18f66f4009f6b073d6f upstream.
+
The longest length of a symbol (KSYM_NAME_LEN) was increased to 512
in the reference [1]. This patch adds kunit test suite to check the longest
symbol length. These tests verify that the longest symbol length defined
@@ lib/Kconfig.debug: config FORTIFY_KUNIT_TEST
depends on HAVE_HW_BREAKPOINT
## lib/Makefile ##
-@@ lib/Makefile: obj-$(CONFIG_FORTIFY_KUNIT_TEST) += fortify_kunit.o
- obj-$(CONFIG_CRC_KUNIT_TEST) += crc_kunit.o
- obj-$(CONFIG_SIPHASH_KUNIT_TEST) += siphash_kunit.o
- obj-$(CONFIG_USERCOPY_KUNIT_TEST) += usercopy_kunit.o
+@@ lib/Makefile: obj-$(CONFIG_OVERFLOW_KUNIT_TEST) += overflow_kunit.o
+ CFLAGS_stackinit_kunit.o += $(call cc-disable-warning, switch-unreachable)
+ obj-$(CONFIG_STACKINIT_KUNIT_TEST) += stackinit_kunit.o
+ obj-$(CONFIG_FORTIFY_KUNIT_TEST) += fortify_kunit.o
+obj-$(CONFIG_LONGEST_SYM_KUNIT_TEST) += longest_symbol_kunit.o
+CFLAGS_longest_symbol_kunit.o += $(call cc-disable-warning, missing-prototypes)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2025-06-25 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 16:58 [PATCH v2 6.1.y 0/2] Kunit to check the longest symbol length Sergio González Collado
2025-06-24 16:58 ` [PATCH v2 6.1.y 1/2] " Sergio González Collado
2025-06-25 14:07 ` Sasha Levin [this message]
2025-06-24 16:58 ` [PATCH v2 6.1.y 2/2] x86/tools: Drop duplicate unlikely() definition in insn_decoder_test.c Sergio González Collado
2025-06-25 14:07 ` Sasha Levin
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=20250624212005-4e6f8fdd63735ebb@stable.kernel.org \
--to=sashal@kernel.org \
--cc=sergio.collado@gmail.com \
--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 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).