From: Marc Zyngier <marc.zyngier@arm.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Christoffer Dall <christoffer.dall@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [WRONG] KVM: arm/arm64: vgic: fix off-by-one bug in vgic_get_irq()
Date: Wed, 19 Dec 2018 16:14:10 +0000 [thread overview]
Message-ID: <f87c9c81-37ab-48eb-4031-dca89f8fce37@arm.com> (raw)
In-Reply-To: <20181219151149.GA6524@embeddedor>
Hi Gustavo,
On 19/12/2018 15:11, Gustavo A. R. Silva wrote:
> Hi Marc,
>
> This is wrong: commit 6022fcc0e87a0eb5e9a72b15ed70dd29ebcb7343
>
> The above is not my original patch and it should not be tagged for stable,
> as it introduces the same kind of bug I intended to fix:
>
> array_index_nospec() can now return kvm->arch.vgic.nr_spis + VGIC_NR_PRIVATE_IRQS
> and this is not what you want. So, in this case the following line of code
> is just fine as it is:
>
> intid = array_index_nospec(intid, kvm->arch.vgic.nr_spis + VGIC_NR_PRIVATE_IRQS);
>
>
> As the commit log says, my patch fixes:
>
> commit 41b87599c74300027f305d7b34368ec558978ff2
>
> not both:
>
> commit 41b87599c74300027f305d7b34368ec558978ff2
>
> and
>
> commit bea2ef803ade3359026d5d357348842bca9edcf1
>
> If you want to apply the fix on top of bea2ef803ade3359026d5d357348842bca9edcf1
> then you should apply this instead:
>
> diff --git a/virt/kvm/arm/vgic/vgic.c b/virt/kvm/arm/vgic/vgic.c
> index bb1a83345741..e607547c7bb0 100644
> --- a/virt/kvm/arm/vgic/vgic.c
> +++ b/virt/kvm/arm/vgic/vgic.c
> @@ -103,7 +103,7 @@ struct vgic_irq *vgic_get_irq(struct kvm *kvm, struct kvm_vcpu *vcpu,
> {
> /* SGIs and PPIs */
> if (intid <= VGIC_MAX_PRIVATE) {
> - intid = array_index_nospec(intid, VGIC_MAX_PRIVATE);
> + intid = array_index_nospec(intid, VGIC_MAX_PRIVATE + 1);
> return &vcpu->arch.vgic_cpu.private_irqs[intid];
> }
>
>
> The commit log should remain the same.
I indeed completely fscked up the conflict resolution, clearly not
engaging my brain. I'll fix that quickly.
Thanks for the heads up.
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2018-12-19 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 15:11 Gustavo A. R. Silva
2018-12-19 16:14 ` Marc Zyngier [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=f87c9c81-37ab-48eb-4031-dca89f8fce37@arm.com \
--to=marc.zyngier@arm.com \
--cc=christoffer.dall@arm.com \
--cc=gustavo@embeddedor.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=stable@vger.kernel.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
Powered by JetHome