public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, sergio.collado@gmail.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12.y 1/2] Kunit to check the longest symbol length
Date: Sun,  8 Jun 2025 22:34:47 -0400	[thread overview]
Message-ID: <20250608131215-7093ad8121be4690@stable.kernel.org> (raw)
In-Reply-To: <20250608145450.7024-2-sergio.collado@gmail.com>

[ Sasha's backport helper bot ]

Hi,

Summary of potential issues:
⚠️ Found matching upstream commit but patch is missing proper reference to it
⚠️ Found follow-up fixes in mainline

Found matching upstream commit: c104c16073b7fdb3e4eae18f66f4009f6b073d6f

Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.14.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:  39ce5e9e3c965 Kunit to check the longest symbol length
    @@ Metadata
      ## Commit message ##
         Kunit to check the longest symbol length
     
    +    commit c104c16073b7 ("Kunit to check the longest symbol length") 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
    @@ Commit message
         Reviewed-by: Rae Moar <rmoar@google.com>
         Signed-off-by: Sergio González Collado <sergio.collado@gmail.com>
         Link: https://github.com/Rust-for-Linux/linux/issues/504
    -    Reviewed-by: Rae Moar <rmoar@google.com>
         Acked-by: David Gow <davidgow@google.com>
         Signed-off-by: Shuah Khan <shuah@kernel.org>
     
    @@ 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
    +@@ lib/Makefile: CFLAGS_fortify_kunit.o += $(DISABLE_STRUCTLEAK_PLUGIN)
    + obj-$(CONFIG_FORTIFY_KUNIT_TEST) += fortify_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
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y       |  Success    |  Success   |

  parent reply	other threads:[~2025-06-09  2:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-08 14:54 [PATCH 6.12.y 0/2] Kunit to check the longest symbol length Sergio González Collado
2025-06-08 14:54 ` [PATCH 6.12.y 1/2] " 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 [this message]
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=20250608131215-7093ad8121be4690@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