From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu] target/ppc: Yet another fix for KVM-HV HPTE accessors
Date: Thu, 11 Jan 2018 18:52:00 +1100 [thread overview]
Message-ID: <20180111075200.GG24770@umbus.fritz.box> (raw)
In-Reply-To: <20180111040832.28383-1-aik@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 2758 bytes --]
On Thu, Jan 11, 2018 at 03:08:32PM +1100, Alexey Kardashevskiy wrote:
> As stated in the 1ad9f0a464fe commit log, the returned entries are not
> a while PTEG. It was not a problem before 1ad9f0a464fe as it would read
> a single record assuming it contains a whole PTEG but now the code tries
> reading the entire PTEG and "if ((n - i) < invalid)" produces negative
> values which then are converted to size_t for memset() and that throws
> seg fault.
>
> This fixes the math.
>
> While here, fix the last @i increment as well.
>
> Fixes: 1ad9f0a464fe "target/ppc: Fix KVM-HV HPTE accessors"
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Applied, thanks.
> ---
>
> Record #0:
> (gdb) p *hdr
> $13 = {
> index = <ptr>,
> n_valid = 0x1,
> n_invalid = 0x6
> }
>
> Record #1:
> (gdb) p *hdr
> $18 = {
> index = <ptr>,
> n_valid = 0x2,
> n_invalid = 0x6
> }
>
>
> i.e. in the second iteration of the loop right before
> "if ((n - i) < invalid)":
> (gdb) p n
> $16 = 0x8
> (gdb) p i
> $17 = 0x9
>
> and @invalid becomes -1.
>
> ---
> target/ppc/kvm.c | 11 +++++++----
> 1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/target/ppc/kvm.c b/target/ppc/kvm.c
> index 0566af7..c2dea81 100644
> --- a/target/ppc/kvm.c
> +++ b/target/ppc/kvm.c
> @@ -2657,21 +2657,24 @@ void kvmppc_read_hptes(ppc_hash_pte64_t *hptes, hwaddr ptex, int n)
>
> hdr = (struct kvm_get_htab_header *)buf;
> while ((i < n) && ((char *)hdr < (buf + rc))) {
> - int invalid = hdr->n_invalid;
> + int invalid = hdr->n_invalid, valid = hdr->n_valid;
>
> if (hdr->index != (ptex + i)) {
> hw_error("kvmppc_read_hptes: Unexpected HPTE index %"PRIu32
> " != (%"HWADDR_PRIu" + %d", hdr->index, ptex, i);
> }
>
> - memcpy(hptes + i, hdr + 1, HASH_PTE_SIZE_64 * hdr->n_valid);
> - i += hdr->n_valid;
> + if (n - i < valid) {
> + valid = n - i;
> + }
> + memcpy(hptes + i, hdr + 1, HASH_PTE_SIZE_64 * valid);
> + i += valid;
>
> if ((n - i) < invalid) {
> invalid = n - i;
> }
> memset(hptes + i, 0, invalid * HASH_PTE_SIZE_64);
> - i += hdr->n_invalid;
> + i += invalid;
>
> hdr = (struct kvm_get_htab_header *)
> ((char *)(hdr + 1) + HASH_PTE_SIZE_64 * hdr->n_valid);
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-11 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 4:08 [Qemu-devel] [PATCH qemu] target/ppc: Yet another fix for KVM-HV HPTE accessors Alexey Kardashevskiy
2018-01-11 7:52 ` David Gibson [this message]
2018-01-11 8:06 ` Mark Cave-Ayland
2018-01-11 9:49 ` David Gibson
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=20180111075200.GG24770@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).