stable.vger.kernel.org archive mirror
 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 3/3] btf: Avoid weak external references
Date: Fri,  6 Dec 2024 12:11:49 -0500	[thread overview]
Message-ID: <20241206110919-ebe1c8e70462f06a@stable.kernel.org> (raw)
In-Reply-To: <20241206085810.112341-4-chenhuacai@loongson.cn>

[ Sasha's backport helper bot ]

Hi,

The upstream commit SHA1 provided is correct: fc5eb4a84e4c063e75a6a6e92308e9533c0f19b5

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.12.y | Present (exact SHA1)
6.6.y | Not found

Note: The patch differs from the upstream commit:
---
1:  fc5eb4a84e4c0 ! 1:  0637e4a3f4e0a btf: Avoid weak external references
    @@ Metadata
      ## Commit message ##
         btf: Avoid weak external references
     
    +    [ Upstream commit fc5eb4a84e4c063e75a6a6e92308e9533c0f19b5 ]
    +
         If the BTF code is enabled in the build configuration, the start/stop
         BTF markers are guaranteed to exist. Only when CONFIG_DEBUG_INFO_BTF=n,
         the references in btf_parse_vmlinux() will remain unsatisfied, relying
    @@ Commit message
         Acked-by: Arnd Bergmann <arnd@arndb.de>
         Acked-by: Jiri Olsa <jolsa@kernel.org>
         Link: https://lore.kernel.org/bpf/20240415162041.2491523-8-ardb+git@google.com
    +    Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
     
      ## kernel/bpf/btf.c ##
     @@ kernel/bpf/btf.c: static struct btf *btf_parse(const union bpf_attr *attr, bpfptr_t uattr, u32 uat
---

Results of testing on various branches:

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

  reply	other threads:[~2024-12-06 17:11 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
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 [this message]
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=20241206110919-ebe1c8e70462f06a@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 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).