From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: mrezanin@redhat.com, qemu-devel@nongnu.org
Subject: Re: [RHEL7 qemu-kvm PATCH 2/3] s390x: Fix vm name copy length
Date: Mon, 11 Jan 2021 13:10:07 +0100 [thread overview]
Message-ID: <5acb5521-fdd2-e511-9cc3-176086183dd5@redhat.com> (raw)
In-Reply-To: <e1ad733af7b23929456d05aacae693ce6462d4b3.1610364304.git.mrezanin@redhat.com>
Hi Miroslav,
On 1/11/21 12:30 PM, mrezanin@redhat.com wrote:
> From: Miroslav Rezanina <mrezanin@redhat.com>
>
> There are two cases when vm name is copied but closing \0 can be lost
> in case name is too long (>=256 characters).
>
> Updating length to copy so there is space for closing \0.
>
> Signed-off-by: Miroslav Rezanina <mrezanin@redhat.com>
> ---
> target/s390x/kvm.c | 2 +-
> target/s390x/misc_helper.c | 4 +++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/target/s390x/kvm.c b/target/s390x/kvm.c
> index b8385e6b95..2313b5727e 100644
> --- a/target/s390x/kvm.c
> +++ b/target/s390x/kvm.c
> @@ -1918,7 +1918,7 @@ static void insert_stsi_3_2_2(S390CPU *cpu, __u64 addr, uint8_t ar)
> */
> if (qemu_name) {
> strncpy((char *)sysib.ext_names[0], qemu_name,
> - sizeof(sysib.ext_names[0]));
> + sizeof(sysib.ext_names[0]) - 1);
> } else {
> strcpy((char *)sysib.ext_names[0], "KVMguest");
> }
What about using strpadcpy() instead?
strpadcpy((char *)sysib.sysib_322.ext_names[0],
sizeof(sysib.sysib_322.ext_names[0]),
qemu_name ?: "KVMguest", '\0');
> diff --git a/target/s390x/misc_helper.c b/target/s390x/misc_helper.c
> index 58dbc023eb..7c478b9e58 100644
> --- a/target/s390x/misc_helper.c
> +++ b/target/s390x/misc_helper.c
> @@ -369,8 +369,10 @@ uint32_t HELPER(stsi)(CPUS390XState *env, uint64_t a0, uint64_t r0, uint64_t r1)
> ebcdic_put(sysib.sysib_322.vm[0].name, qemu_name,
> MIN(sizeof(sysib.sysib_322.vm[0].name),
> strlen(qemu_name)));
> + memset((char *)sysib.sysib_322.ext_names[0], 0,
> + sizeof(sysib.sysib_322.ext_names[0]));
> strncpy((char *)sysib.sysib_322.ext_names[0], qemu_name,
> - sizeof(sysib.sysib_322.ext_names[0]));
> + sizeof(sysib.sysib_322.ext_names[0]) - 1);
And here:
strpadcpy((char *)sysib.sysib_322.ext_names[0],
sizeof(sysib.sysib_322.ext_names[0]),
qemu_name, '\0');
> } else {
> ebcdic_put(sysib.sysib_322.vm[0].name, "TCGguest", 8);
> strcpy((char *)sysib.sysib_322.ext_names[0], "TCGguest");
>
next prev parent reply other threads:[~2021-01-11 12:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 11:30 [RHEL7 qemu-kvm PATCH 0/3] Fixing several GCC 11 warnings mrezanin
2021-01-11 11:30 ` [RHEL7 qemu-kvm PATCH 1/3] Fix net.c warning on GCC 11 mrezanin
2021-01-11 11:30 ` [RHEL7 qemu-kvm PATCH 2/3] s390x: Fix vm name copy length mrezanin
2021-01-11 12:10 ` Philippe Mathieu-Daudé [this message]
2021-01-11 12:24 ` Thomas Huth
2021-01-11 12:42 ` Miroslav Rezanina
2021-01-11 12:54 ` Thomas Huth
2021-01-11 12:58 ` Miroslav Rezanina
2021-01-11 13:02 ` Christian Borntraeger
2021-01-11 13:07 ` Christian Borntraeger
2021-01-11 13:17 ` Miroslav Rezanina
2021-01-11 13:19 ` Christian Borntraeger
2021-01-11 12:37 ` Miroslav Rezanina
2021-01-11 11:30 ` [RHEL7 qemu-kvm PATCH 3/3] Fix tcg_out_op argument mismatch warning mrezanin
2021-01-11 12:15 ` Philippe Mathieu-Daudé
2021-01-11 12:40 ` Miroslav Rezanina
2021-01-11 11:39 ` [RHEL7 qemu-kvm PATCH 0/3] Fixing several GCC 11 warnings no-reply
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=5acb5521-fdd2-e511-9cc3-176086183dd5@redhat.com \
--to=philmd@redhat.com \
--cc=mrezanin@redhat.com \
--cc=qemu-devel@nongnu.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).