From: Avi Kivity <avi@redhat.com>
To: paulmck@linux.vnet.ibm.com
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: use the correct RCU API
Date: Wed, 21 Apr 2010 11:22:53 +0300 [thread overview]
Message-ID: <4BCEB5DD.1000701@redhat.com> (raw)
In-Reply-To: <20100420215529.GA21246@linux.vnet.ibm.com>
On 04/21/2010 12:55 AM, Paul E. McKenney wrote:
> On Mon, Apr 19, 2010 at 05:41:23PM +0800, Lai Jiangshan wrote:
>
>> The RCU/SRCU API have already changed for proving RCU usage.
>>
>> I got the following dmesg when PROVE_RCU=y because we used incorrect API.
>> This patch coverts rcu_deference() to srcu_dereference() or family API.
>>
>> ===================================================
>> [ INFO: suspicious rcu_dereference_check() usage. ]
>> ---------------------------------------------------
>> arch/x86/kvm/mmu.c:3020 invoked rcu_dereference_check() without protection!
>>
>> other info that might help us debug this:
>>
>>
>> rcu_scheduler_active = 1, debug_locks = 0
>> 2 locks held by qemu-system-x86/8550:
>> #0: (&kvm->slots_lock){+.+.+.}, at: [<ffffffffa011a6ac>] kvm_set_memory_region+0x29/0x50 [kvm]
>> #1: (&(&kvm->mmu_lock)->rlock){+.+...}, at: [<ffffffffa012262d>] kvm_arch_commit_memory_region+0xa6/0xe2 [kvm]
>>
>> stack backtrace:
>> Pid: 8550, comm: qemu-system-x86 Not tainted 2.6.34-rc4-tip-01028-g939eab1 #27
>> Call Trace:
>> [<ffffffff8106c59e>] lockdep_rcu_dereference+0xaa/0xb3
>> [<ffffffffa012f6c1>] kvm_mmu_calculate_mmu_pages+0x44/0x7d [kvm]
>> [<ffffffffa012263e>] kvm_arch_commit_memory_region+0xb7/0xe2 [kvm]
>> [<ffffffffa011a5d7>] __kvm_set_memory_region+0x636/0x6e2 [kvm]
>> [<ffffffffa011a6ba>] kvm_set_memory_region+0x37/0x50 [kvm]
>> [<ffffffffa015e956>] vmx_set_tss_addr+0x46/0x5a [kvm_intel]
>> [<ffffffffa0126592>] kvm_arch_vm_ioctl+0x17a/0xcf8 [kvm]
>> [<ffffffff810a8692>] ? unlock_page+0x27/0x2c
>> [<ffffffff810bf879>] ? __do_fault+0x3a9/0x3e1
>> [<ffffffffa011b12f>] kvm_vm_ioctl+0x364/0x38d [kvm]
>> [<ffffffff81060cfa>] ? up_read+0x23/0x3d
>> [<ffffffff810f3587>] vfs_ioctl+0x32/0xa6
>> [<ffffffff810f3b19>] do_vfs_ioctl+0x495/0x4db
>> [<ffffffff810e6b2f>] ? fget_light+0xc2/0x241
>> [<ffffffff810e416c>] ? do_sys_open+0x104/0x116
>> [<ffffffff81382d6d>] ? retint_swapgs+0xe/0x13
>> [<ffffffff810f3ba6>] sys_ioctl+0x47/0x6a
>> [<ffffffff810021db>] system_call_fastpath+0x16/0x1b
>>
> I have queued this one up, thank you, Lai!
>
>
I'd like this to go through kvm.git as well.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-04-21 8:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 9:41 [PATCH] kvm: use the correct RCU API Lai Jiangshan
2010-04-19 9:41 ` Lai Jiangshan
2010-04-19 9:49 ` Avi Kivity
2010-04-19 23:35 ` Paul E. McKenney
2010-04-20 2:09 ` Lai Jiangshan
2010-04-20 18:42 ` Paul E. McKenney
2010-04-19 9:58 ` [BUG] kvm: dereference srcu-protected pointer without srcu_read_lock() held Lai Jiangshan
2010-04-19 10:08 ` Avi Kivity
2010-04-20 1:45 ` Marcelo Tosatti
2010-04-20 6:29 ` Lai Jiangshan
2010-04-20 22:21 ` Paul E. McKenney
2010-04-21 8:17 ` Avi Kivity
2010-04-21 14:36 ` Paul E. McKenney
2010-04-20 21:55 ` [PATCH] kvm: use the correct RCU API Paul E. McKenney
2010-04-21 8:22 ` Avi Kivity [this message]
2010-04-21 8:22 ` Avi Kivity
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=4BCEB5DD.1000701@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=paulmck@linux.vnet.ibm.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 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.