From: David Gibson <david@gibson.dropbear.id.au>
To: Thomas Huth <thuth@redhat.com>
Cc: kvm-ppc@vger.kernel.org, Paul Mackerras <paulus@samba.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:37:08 +1000 [thread overview]
Message-ID: <20150921013708.GF20331@voom.fritz.box> (raw)
In-Reply-To: <1442559448-1947-1-git-send-email-thuth@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2325 bytes --]
On Fri, Sep 18, 2015 at 08:57:28AM +0200, Thomas Huth wrote:
> Access to the kvm->buses (like with the kvm_io_bus_read() and -write()
> functions) has to be protected via the kvm->srcu lock.
> The kvmppc_h_logical_ci_load() and -store() functions are missing
> this lock so far, so let's add it there, too.
> This fixes the problem that the kernel reports "suspicious RCU usage"
> when lock debugging is enabled.
>
> Fixes: 99342cf8044420eebdf9297ca03a14cb6a7085a1
> Signed-off-by: Thomas Huth <thuth@redhat.com>
Nice catch. Looks like I missed this because the places
kvm_io_bus_{read,write}() are called on x86 are buried about 5 layers
below where the srcu lock is taken :/.
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> arch/powerpc/kvm/book3s.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/powerpc/kvm/book3s.c b/arch/powerpc/kvm/book3s.c
> index d75bf32..096e5eb 100644
> --- a/arch/powerpc/kvm/book3s.c
> +++ b/arch/powerpc/kvm/book3s.c
> @@ -828,12 +828,15 @@ int kvmppc_h_logical_ci_load(struct kvm_vcpu *vcpu)
> unsigned long size = kvmppc_get_gpr(vcpu, 4);
> unsigned long addr = kvmppc_get_gpr(vcpu, 5);
> u64 buf;
> + int srcu_idx;
> int ret;
>
> if (!is_power_of_2(size) || (size > sizeof(buf)))
> return H_TOO_HARD;
>
> + srcu_idx = srcu_read_lock(&vcpu->kvm->srcu);
> ret = kvm_io_bus_read(vcpu, KVM_MMIO_BUS, addr, size, &buf);
> + srcu_read_unlock(&vcpu->kvm->srcu, srcu_idx);
> if (ret != 0)
> return H_TOO_HARD;
>
> @@ -868,6 +871,7 @@ int kvmppc_h_logical_ci_store(struct kvm_vcpu *vcpu)
> unsigned long addr = kvmppc_get_gpr(vcpu, 5);
> unsigned long val = kvmppc_get_gpr(vcpu, 6);
> u64 buf;
> + int srcu_idx;
> int ret;
>
> switch (size) {
> @@ -891,7 +895,9 @@ int kvmppc_h_logical_ci_store(struct kvm_vcpu *vcpu)
> return H_TOO_HARD;
> }
>
> + srcu_idx = srcu_read_lock(&vcpu->kvm->srcu);
> ret = kvm_io_bus_write(vcpu, KVM_MMIO_BUS, addr, size, &buf);
> + srcu_read_unlock(&vcpu->kvm->srcu, srcu_idx);
> if (ret != 0)
> return H_TOO_HARD;
>
--
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: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-09-21 1:36 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 [this message]
2015-09-21 5:50 ` Paolo Bonzini
2015-09-21 7:59 ` Paul Mackerras
2015-09-21 9:30 ` Paolo Bonzini
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=20150921013708.GF20331@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@samba.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).