All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Huacai Chen <chenhuacai@loongson.cn>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1&6.6 1/3] kallsyms: Avoid weak references for kallsyms symbols
Date: Fri,  7 Feb 2025 17:50:56 -0500	[thread overview]
Message-ID: <20250207165807-194d564469854d1c@stable.kernel.org> (raw)
In-Reply-To: <20241206085810.112341-2-chenhuacai@loongson.cn>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: 951bcae6c5a0bfaa55b27c5f16178204988f0379

WARNING: Author mismatch between patch and upstream commit:
Backport author: Huacai Chen<chenhuacai@loongson.cn>
Commit author: Ard Biesheuvel<ardb@kernel.org>


Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Not found

Note: The patch differs from the upstream commit:
---
1:  951bcae6c5a0b ! 1:  d6ccfcaa675df kallsyms: Avoid weak references for kallsyms symbols
    @@ Metadata
      ## Commit message ##
         kallsyms: Avoid weak references for kallsyms symbols
     
    +    [ Upstream commit 951bcae6c5a0bfaa55b27c5f16178204988f0379 ]
    +
         kallsyms is a directory of all the symbols in the vmlinux binary, and so
         creating it is somewhat of a chicken-and-egg problem, as its non-zero
         size affects the layout of the binary, and therefore the values of the
    @@ Commit message
         Link: https://lkml.kernel.org/r/20230504174320.3930345-1-ardb%40kernel.org
         Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
         Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
    +    Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
     
      ## include/asm-generic/vmlinux.lds.h ##
     @@
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y        |  Success    |  Failed    |
| stable/linux-6.1.y        |  Success    |  Failed    |

Build Errors:
Build error for stable/linux-6.6.y:
    ssh: connect to host 192.168.1.58 port 22: No route to host

Build error for stable/linux-6.1.y:
    ssh: connect to host 192.168.1.58 port 22: No route to host

  parent reply	other threads:[~2025-02-07 22:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06  8:58 [PATCH 6.1&6.6 0/3] kbuild: Avoid weak external linkage where possible Huacai Chen
2024-12-06  8:58 ` [PATCH 6.1&6.6 1/3] kallsyms: Avoid weak references for kallsyms symbols Huacai Chen
2024-12-06 17:11   ` Sasha Levin
2025-02-07 22:50   ` Sasha Levin [this message]
2024-12-06  8:58 ` [PATCH 6.1&6.6 2/3] vmlinux: Avoid weak reference to notes section Huacai Chen
2024-12-06 17:11   ` Sasha Levin
2024-12-06  8:58 ` [PATCH 6.1&6.6 3/3] btf: Avoid weak external references Huacai Chen
2024-12-06 17:11   ` Sasha Levin
2024-12-06 13:04 ` [PATCH 6.1&6.6 0/3] kbuild: Avoid weak external linkage where possible Greg Kroah-Hartman
2024-12-07  9:21   ` Huacai Chen
2024-12-07  9:32     ` Greg Kroah-Hartman
2024-12-07 10:46       ` Xi Ruoyao
2024-12-09  8:31         ` Ard Biesheuvel
2024-12-09 10:01           ` Xi Ruoyao
2025-02-06  8:37   ` WangYuli
2025-02-06  9:31     ` Ard Biesheuvel
2025-02-06 10:03     ` Greg KH
2025-09-05  6:49       ` Ming Wang
2025-09-05  7:09         ` Greg KH
2025-09-05  8:29           ` Ming Wang

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=20250207165807-194d564469854d1c@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=chenhuacai@loongson.cn \
    --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.