From: Clark Williams <clrkwllms@kernel.org>
To: stable@vger.kernel.org
Cc: bpf@vger.kernel.org, x86@ekrnel.org, kvm@vger.kernel.org
Subject: [PATCH v2 1/2] tools/lib/bpf: fix const-qualifier discard in resolve_full_path
Date: Tue, 16 Jun 2026 20:13:01 -0500 [thread overview]
Message-ID: <20260617011303.3969027-2-clrkwllms@kernel.org> (raw)
In-Reply-To: <20260617011303.3969027-1-clrkwllms@kernel.org>
[ Upstream commit d70f79fef65810faf64dbae1f3a1b5623cdb2345 ]
strchr() now propagates const when passed a const char * argument in
newer GCC/glibc combinations, causing -Werror=discarded-qualifiers to
fire on the assignment to next_path. Declare next_path as const char *
since it is only used for pointer arithmetic, never written through.
[ clrkwllms: only the next_path change from the upstream commit applies
to 6.1.y ]
Assisted-by: Claude:claude-sonnet-4.6
Signed-off-by: Clark Williams <clrkwllms@kernel.org>
---
tools/lib/bpf/libbpf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
index 7bd6aff6e260..33b214a91338 100644
--- a/tools/lib/bpf/libbpf.c
+++ b/tools/lib/bpf/libbpf.c
@@ -10748,7 +10748,7 @@ static int resolve_full_path(const char *file, char *result, size_t result_sz)
if (!search_paths[i])
continue;
for (s = search_paths[i]; s != NULL; s = strchr(s, ':')) {
- char *next_path;
+ const char *next_path;
int seg_len;
if (s[0] == ':')
--
2.54.0
next prev parent reply other threads:[~2026-06-17 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 1:13 [PATCH v2 0/2] linux-6.1.y: fix build errors with newer GCC/glibc Clark Williams
2026-06-17 1:13 ` Clark Williams [this message]
2026-06-17 3:10 ` [PATCH v2 1/2] tools/lib/bpf: fix const-qualifier discard in resolve_full_path Alexei Starovoitov
2026-06-17 1:13 ` [PATCH v2 2/2] KVM: VMX: guard regparm(0) on vmread_error_trampoline for x86_32 only Clark Williams
2026-06-17 11:20 ` Hanne-Lotta Mäenpää
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=20260617011303.3969027-2-clrkwllms@kernel.org \
--to=clrkwllms@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=x86@ekrnel.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