From: Greg KH <gregkh@linuxfoundation.org>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: stable@vger.kernel.org, Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH v4.9 backport] KVM: arm/arm64: vgic-its: Preserve the revious read from the pending table
Date: Thu, 14 Dec 2017 22:26:47 +0100 [thread overview]
Message-ID: <20171214212647.GA27981@kroah.com> (raw)
In-Reply-To: <20171214210424.25740-3-christoffer.dall@linaro.org>
On Thu, Dec 14, 2017 at 10:04:23PM +0100, Christoffer Dall wrote:
> From: Marc Zyngier <marc.zyngier@arm.com>
>
> Commit 64afe6e9eb4841f35317da4393de21a047a883b3 upstream.
>
> The current pending table parsing code assumes that we keep the
> previous read of the pending bits, but keep that variable in
> the current block, making sure it is discarded on each loop.
>
> We end-up using whatever is on the stack. Who knows, it might
> just be the right thing...
>
> Fixes: 33d3bc9556a7d ("KVM: arm64: vgic-its: Read initial LPI pending table")
> Cc: <stable@vger.kernel.org> # 4.8
> Reported-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
> ---
> virt/kvm/arm/vgic/vgic-its.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Now applied, thanks.
greg k-h
next prev parent reply other threads:[~2017-12-14 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 21:04 [PATCH v4.9 backport] KVM: arm/arm64: vgic-its: Preserve the revious read from the pending table Christoffer Dall
2017-12-14 21:26 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-12 16:42 Christoffer Dall
2017-12-12 16:53 ` Christoffer Dall
2017-12-12 16:55 ` Christoffer Dall
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=20171214212647.GA27981@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=christoffer.dall@linaro.org \
--cc=marc.zyngier@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;
as well as URLs for NNTP newsgroup(s).