From: Gautam Menghani <gautam@linux.ibm.com>
To: Amit Machhiwal <amachhiw@linux.ibm.com>
Cc: Harsh Prateek Bora <harshpb@linux.ibm.com>,
qemu-ppc@nongnu.org, Vaibhav Jain <vaibhav@linux.ibm.com>,
Chinmay Rath <rathc@linux.ibm.com>,
Glenn Miles <milesg@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Nicholas Piggin <npiggin@gmail.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH v2] target/ppc/kvm: Fix const violation when trimming CPU alias suffix
Date: Fri, 8 May 2026 20:10:18 +0530 [thread overview]
Message-ID: <af310sWYO_VGZAVB@Gautams-MacBook-Pro.local> (raw)
In-Reply-To: <20260508081416.1014-1-amachhiw@linux.ibm.com>
On Fri, May 08, 2026 at 01:44:16PM +0530, Amit Machhiwal wrote:
> GCC 16 tightens diagnostics around const correctness and now correctly
> rejects attempts to modify strings referenced through const-qualified
> pointers. In kvm_ppc_register_host_cpu_type(), ppc_cpu_aliases[i].model
> is declared as const char *, but the code was using strstr() on it and
> then modifying the returned pointer in place to strip
> POWERPC_CPU_TYPE_SUFFIX.
>
> This results in a write through a pointer derived from const data,
> triggering a build failure with GCC 16:
>
> error: assignment discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
> suffix = strstr(ppc_cpu_aliases[i].model, POWERPC_CPU_TYPE_SUFFIX);
> ^
>
> Fix this by duplicating the model string into a mutable buffer using
> g_strdup(), trimming the suffix on that temporary buffer, and only then
> storing it in the alias table.
>
> This preserves the existing behavior while avoiding modification of
> const data and ensures compatibility with newer compilers.
>
> No functional change intended.
>
> Signed-off-by: Amit Machhiwal <amachhiw@linux.ibm.com>
> ---
> Changes in v2:
> * trim the duplicated buffer before assigning it to ppc_cpu_aliases[i].model
> ---
>
> target/ppc/kvm.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/target/ppc/kvm.c b/target/ppc/kvm.c
> index 25c28ad089c6..c2843b1421cb 100644
> --- a/target/ppc/kvm.c
> +++ b/target/ppc/kvm.c
> @@ -2654,13 +2654,14 @@ static int kvm_ppc_register_host_cpu_type(void)
> dc = DEVICE_CLASS(ppc_cpu_get_family_class(pvr_pcc));
> for (i = 0; ppc_cpu_aliases[i].alias != NULL; i++) {
> if (g_ascii_strcasecmp(ppc_cpu_aliases[i].alias, dc->desc) == 0) {
> - char *suffix;
> + char *model, *suffix;
>
> - ppc_cpu_aliases[i].model = g_strdup(object_class_get_name(oc));
> - suffix = strstr(ppc_cpu_aliases[i].model, POWERPC_CPU_TYPE_SUFFIX);
> + model = g_strdup(object_class_get_name(oc));
> + suffix = strstr(model, POWERPC_CPU_TYPE_SUFFIX);
> if (suffix) {
> *suffix = 0;
> }
> + ppc_cpu_aliases[i].model = model;
> break;
> }
> }
>
Reviewed-by: Gautam Menghani <gautam@linux.ibm.com>
> base-commit: ee7eb612be8f8886d48c1d0c1f1c65e495138f83
> --
> 2.50.1 (Apple Git-155)
>
>
prev parent reply other threads:[~2026-05-08 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 8:14 [PATCH v2] target/ppc/kvm: Fix const violation when trimming CPU alias suffix Amit Machhiwal
2026-05-08 14:40 ` Gautam Menghani [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=af310sWYO_VGZAVB@Gautams-MacBook-Pro.local \
--to=gautam@linux.ibm.com \
--cc=amachhiw@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=milesg@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rathc@linux.ibm.com \
--cc=vaibhav@linux.ibm.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