[ 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: 6ad4997209cb)
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: 8aeaf1169468f 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
## lib/Makefile ## @@ lib/Makefile: obj-$(CONFIG_FORTIFY_KUNIT_TEST) += fortify_kunit.o - obj-$(CONFIG_CRC_KUNIT_TEST) += crc_kunit.o + obj-$(CONFIG_STRCAT_KUNIT_TEST) += strcat_kunit.o + obj-$(CONFIG_STRSCPY_KUNIT_TEST) += strscpy_kunit.o obj-$(CONFIG_SIPHASH_KUNIT_TEST) += siphash_kunit.o - obj-$(CONFIG_USERCOPY_KUNIT_TEST) += usercopy_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.6.y | Success | Success |