linux-kernel - Re: [PATCH v3 1/3] KVM: fix rcu usage warning in kvm_arch_vcpu_ioctl_set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 19 Jan 2011 13:16:23 +0800
From:	Xiao Guangrong <xiaoguangrong@...fujitsu.com>
To:	Avi Kivity <avi@...hat.com>
CC:	Marcelo Tosatti <mtosatti@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>, KVM <kvm@...r.kernel.org>
Subject: Re: [PATCH v3 1/3] KVM: fix rcu usage warning in kvm_arch_vcpu_ioctl_set_sregs()

On 01/12/2011 03:39 PM, Xiao Guangrong wrote:
> Fix:
> 
> [ 1001.499596] ===================================================
> [ 1001.499599] [ INFO: suspicious rcu_dereference_check() usage. ]
> [ 1001.499601] ---------------------------------------------------
> [ 1001.499604] include/linux/kvm_host.h:301 invoked rcu_dereference_check() without protection!
> 	......
> [ 1001.499636] Pid: 6035, comm: qemu-system-x86 Not tainted 2.6.37-rc6+ #62
> [ 1001.499638] Call Trace:
> [ 1001.499644]  [] lockdep_rcu_dereference+0x9d/0xa5
> [ 1001.499653]  [] gfn_to_memslot+0x8d/0xc8 [kvm]
> [ 1001.499661]  [] gfn_to_hva+0x16/0x3f [kvm]
> [ 1001.499669]  [] kvm_read_guest_page+0x1e/0x5e [kvm]
> [ 1001.499681]  [] kvm_read_guest_page_mmu+0x53/0x5e [kvm]
> [ 1001.499699]  [] load_pdptrs+0x3f/0x9c [kvm]
> [ 1001.499705]  [] ? vmx_set_cr0+0x507/0x517 [kvm_intel]
> [ 1001.499717]  [] kvm_arch_vcpu_ioctl_set_sregs+0x1f3/0x3c0 [kvm]
> [ 1001.499727]  [] kvm_vcpu_ioctl+0x6a5/0xbc5 [kvm]
> 
> Signed-off-by: Xiao Guangrong <xiaoguangrong@...fujitsu.com>

Ping ...?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/