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 0/2] linux-6.1.y: fix build errors with newer GCC/glibc
Date: Tue, 16 Jun 2026 20:13:00 -0500 [thread overview]
Message-ID: <20260617011303.3969027-1-clrkwllms@kernel.org> (raw)
Please apply to linux-6.1.y.
Two build fixes for newer toolchains (GCC 15+ / glibc 2.43+):
1) tools/lib/bpf: strchr() now propagates const in newer glibc,
causing -Werror=discarded-qualifiers on next_path in
resolve_full_path(). Equivalent to upstream commit d70f79fef658.
2) KVM: VMX: regparm(0) on vmread_error_trampoline is a no-op on
x86-64 and newer GCC emits -Wattributes for it. Guard with
CONFIG_X86_32. Simpler equivalent of upstream commit 0b5e7a16a0a7
which redesigns the declaration entirely.
Changes since v1:
- Fixed Assisted-by tag format per coding-assistants.html
- Added upstream commit references per stable-kernel-rules.html
- Updated KVM subsystem prefix to conventional KVM: VMX: style
- Fixed Author/Signed-off-by email mismatch
Clark Williams (2):
tools/lib/bpf: fix const-qualifier discard in resolve_full_path
KVM: VMX: guard regparm(0) on vmread_error_trampoline for x86_32 only
arch/x86/kvm/vmx/vmx_ops.h | 7 +++++--
tools/lib/bpf/libbpf.c | 2 +-
2 files changed, 6 insertions(+), 3 deletions(-)
base-commit: 228da13e907e2b46b7222cfc35290fbfad920bef
--
2.54.0
next reply other threads:[~2026-06-17 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 1:13 Clark Williams [this message]
2026-06-17 1:13 ` [PATCH v2 1/2] tools/lib/bpf: fix const-qualifier discard in resolve_full_path Clark Williams
2026-06-17 3:10 ` Alexei Starovoitov
2026-07-02 14:23 ` Greg KH
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-1-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