kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: David Gibson <david@gibson.dropbear.id.au>,
	Thomas Huth <thuth@redhat.com>,
	kvm-ppc@vger.kernel.org, Alexander Graf <agraf@suse.com>,
	kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Take the kvm->srcu lock in kvmppc_h_logical_ci_load/store()
Date: Mon, 21 Sep 2015 11:30:19 +0200	[thread overview]
Message-ID: <55FFCE2B.20308@redhat.com> (raw)
In-Reply-To: <20150921075927.GA7835@fergus.ozlabs.ibm.com>



On 21/09/2015 09:59, Paul Mackerras wrote:
> I was going to send you a
> pull request tomorrow, but if you are about to send stuff off to Linus
> you could pull now from:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git kvm-ppc-fixes

Ok, I'll pull from here tomorrow.  The pull request will go to Linus
around Thursday.

Paolo

> The three patches in there are:
> 
> Gautham R. Shenoy (1):
>       KVM: PPC: Book3S HV: Pass the correct trap argument to kvmhv_commence_exit
> 
> Paul Mackerras (1):
>       KVM: PPC: Book3S HV: Fix handling of interrupted VCPUs
> 
> Thomas Huth (1):
>       KVM: PPC: Book3S: Take the kvm->srcu lock in kvmppc_h_logical_ci_load/store()
> 
> The one from Gautham is a 1-liner that has been around for months and
> got missed, and is obviously correct.  The one from me fixes a
> regression that was introduced in 4.3-rc1 by one of my patches, which
> causes oopses and soft lockups due to a use-after-free bug.

  reply	other threads:[~2015-09-21  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  6:57 [PATCH] KVM: PPC: Take the kvm->srcu lock in kvmppc_h_logical_ci_load/store() Thomas Huth
2015-09-21  1:37 ` David Gibson
2015-09-21  5:50   ` Paolo Bonzini
2015-09-21  7:59     ` Paul Mackerras
2015-09-21  9:30       ` Paolo Bonzini [this message]
2015-09-21  6:50   ` Thomas Huth

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=55FFCE2B.20308@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=paulus@ozlabs.org \
    --cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).