All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Denis Kirjanov <kda@linux-powerpc.org>, kvm-ppc@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org
Subject: Re: suspicious RCU usage with kvm_pr
Date: Wed, 16 Sep 2015 10:16:01 +0000	[thread overview]
Message-ID: <55F94161.7000405@redhat.com> (raw)
In-Reply-To: <CAOJe8K3mu6M48wGAMMQNXPDrkzk+z4j5yzcJ7eRfex0FWcZsQA@mail.gmail.com>

On 16/09/15 10:51, Denis Kirjanov wrote:
> Hi,
> 
> I see the following trace on qemu startup (ps700 blade):
> 
> v4.2-11169-g64d1def
> 
> 
> [  143.369638] ===============> [  143.369640] [ INFO: suspicious RCU usage. ]
> [  143.369643] 4.2.0-11169-g64d1def #10 Tainted: G S
> [  143.369645] -------------------------------
> [  143.369647] arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:3310
> suspicious rcu_dereference_check() usage!
> [  143.369649]
> other info that might help us debug this:
> 
> [  143.369652]
> rcu_scheduler_active = 1, debug_locks = 1
> [  143.369655] 1 lock held by qemu-system-ppc/2292:
> [  143.369656]  #0:  (&vcpu->mutex){+.+.+.}, at: [<d000000004225bac>]
> .vcpu_load+0x2c/0xb0 [kvm]
> [  143.369672]
> stack backtrace:
> [  143.369675] CPU: 12 PID: 2292 Comm: qemu-system-ppc Tainted: G S
>           4.2.0-11169-g64d1def #10
> [  143.369677] Call Trace:
> [  143.369682] [c0000001d08bf200] [c000000000816dd0]
> .dump_stack+0x98/0xd4 (unreliable)
> [  143.369687] [c0000001d08bf280] [c0000000000f7058]
> .lockdep_rcu_suspicious+0x108/0x170
> [  143.369696] [c0000001d08bf310] [d0000000042296d8]
> .kvm_io_bus_read+0x1d8/0x220 [kvm]
> [  143.369705] [c0000001d08bf3c0] [d00000000422f980]
> .kvmppc_h_logical_ci_load+0x60/0xe0 [kvm]

Could it be that we need to srcu_read_lock(&vcpu->kvm->srcu) before
calling the kvm_io_bus_read/write() function in the
kvmppc_h_logical_ci_load/store() function?

 Thomas


WARNING: multiple messages have this Message-ID (diff)
From: Thomas Huth <thuth@redhat.com>
To: Denis Kirjanov <kda@linux-powerpc.org>, kvm-ppc@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org
Subject: Re: suspicious RCU usage with kvm_pr
Date: Wed, 16 Sep 2015 12:16:01 +0200	[thread overview]
Message-ID: <55F94161.7000405@redhat.com> (raw)
In-Reply-To: <CAOJe8K3mu6M48wGAMMQNXPDrkzk+z4j5yzcJ7eRfex0FWcZsQA@mail.gmail.com>

On 16/09/15 10:51, Denis Kirjanov wrote:
> Hi,
> 
> I see the following trace on qemu startup (ps700 blade):
> 
> v4.2-11169-g64d1def
> 
> 
> [  143.369638] ===============================
> [  143.369640] [ INFO: suspicious RCU usage. ]
> [  143.369643] 4.2.0-11169-g64d1def #10 Tainted: G S
> [  143.369645] -------------------------------
> [  143.369647] arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:3310
> suspicious rcu_dereference_check() usage!
> [  143.369649]
> other info that might help us debug this:
> 
> [  143.369652]
> rcu_scheduler_active = 1, debug_locks = 1
> [  143.369655] 1 lock held by qemu-system-ppc/2292:
> [  143.369656]  #0:  (&vcpu->mutex){+.+.+.}, at: [<d000000004225bac>]
> .vcpu_load+0x2c/0xb0 [kvm]
> [  143.369672]
> stack backtrace:
> [  143.369675] CPU: 12 PID: 2292 Comm: qemu-system-ppc Tainted: G S
>           4.2.0-11169-g64d1def #10
> [  143.369677] Call Trace:
> [  143.369682] [c0000001d08bf200] [c000000000816dd0]
> .dump_stack+0x98/0xd4 (unreliable)
> [  143.369687] [c0000001d08bf280] [c0000000000f7058]
> .lockdep_rcu_suspicious+0x108/0x170
> [  143.369696] [c0000001d08bf310] [d0000000042296d8]
> .kvm_io_bus_read+0x1d8/0x220 [kvm]
> [  143.369705] [c0000001d08bf3c0] [d00000000422f980]
> .kvmppc_h_logical_ci_load+0x60/0xe0 [kvm]

Could it be that we need to srcu_read_lock(&vcpu->kvm->srcu) before
calling the kvm_io_bus_read/write() function in the
kvmppc_h_logical_ci_load/store() function?

 Thomas

  reply	other threads:[~2015-09-16 10:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  8:51 suspicious RCU usage with kvm_pr Denis Kirjanov
2015-09-16  8:51 ` Denis Kirjanov
2015-09-16 10:16 ` Thomas Huth [this message]
2015-09-16 10:16   ` Thomas Huth
2015-09-16 10:59   ` Denis Kirjanov
2015-09-16 10:59     ` Denis Kirjanov
2015-09-18 13:13     ` Thomas Huth
2015-09-18 13:13       ` Thomas Huth
2015-09-18 19:54       ` Denis Kirjanov
2015-09-18 19:54         ` Denis Kirjanov

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=55F94161.7000405@redhat.com \
    --to=thuth@redhat.com \
    --cc=kda@linux-powerpc.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.