From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: He Zhe <zhe.he@windriver.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.12.y] libbpf: Prevent compiler warnings/errors
Date: Sun, 13 Apr 2025 12:47:11 -0400 [thread overview]
Message-ID: <20250412091854-fc75ac150750cf4d@stable.kernel.org> (raw)
In-Reply-To: <20250411033644.1156976-1-zhe.he@windriver.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 7f4ec77f3fee41dd6a41f03a40703889e6e8f7b2
WARNING: Author mismatch between patch and upstream commit:
Backport author: He Zhe<zhe.he@windriver.com>
Commit author: Eder Zulian<ezulian@redhat.com>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.13.y | Present (exact SHA1)
Note: The patch differs from the upstream commit:
---
1: 7f4ec77f3fee4 ! 1: 1a7061fb10c80 libbpf: Prevent compiler warnings/errors
@@ Metadata
## Commit message ##
libbpf: Prevent compiler warnings/errors
+ commit 7f4ec77f3fee41dd6a41f03a40703889e6e8f7b2 upstream.
+
Initialize 'new_off' and 'pad_bits' to 0 and 'pad_type' to NULL in
btf_dump_emit_bit_padding to prevent compiler warnings/errors which are
observed when compiling with 'EXTRA_CFLAGS=-g -Og' options, but do not
@@ Commit message
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Acked-by: Jiri Olsa <jolsa@kernel.org>
Link: https://lore.kernel.org/bpf/20241022172329.3871958-3-ezulian@redhat.com
+ Signed-off-by: He Zhe <zhe.he@windriver.com>
+ Signed-off-by: Xiangyu Chen <xiangyu.chen@windriver.com>
## tools/lib/bpf/btf_dump.c ##
@@ tools/lib/bpf/btf_dump.c: static void btf_dump_emit_bit_padding(const struct btf_dump *d,
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
prev parent reply other threads:[~2025-04-13 16:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 3:36 [PATCH 6.12.y] libbpf: Prevent compiler warnings/errors He Zhe
2025-04-13 16:47 ` Sasha Levin [this message]
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=20250412091854-fc75ac150750cf4d@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=zhe.he@windriver.com \
/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).