From: Borislav Petkov <bp@alien8.de>
To: kvm ML <kvm@vger.kernel.org>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: [ 483.545673] include/linux/kvm_host.h:648 suspicious rcu_dereference_check() usage!
Date: Tue, 4 May 2021 12:02:53 +0200 [thread overview]
Message-ID: <YJEbzVjirlgscmLU@zn.tnic> (raw)
Hey folks,
perhaps it is fixed already - kernel is 5.12-rc8+tip/master but lemme
check if you've seen it already:
[ 483.529501] =============================
[ 483.533612] WARNING: suspicious RCU usage
[ 483.537718] 5.12.0-rc8+ #1 Not tainted
[ 483.541566] -----------------------------
[ 483.545673] include/linux/kvm_host.h:648 suspicious rcu_dereference_check() usage!
[ 483.553371]
other info that might help us debug this:
[ 483.561507]
rcu_scheduler_active = 2, debug_locks = 1
[ 483.568155] 1 lock held by qemu-system-x86/3893:
[ 483.572880] #0: ffff888107a580c8 (&vcpu->mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x6d/0x650 [kvm]
[ 483.581980]
stack backtrace:
[ 483.586442] CPU: 2 PID: 3893 Comm: qemu-system-x86 Not tainted 5.12.0-rc8+ #1
[ 483.593704] Hardware name: GIGABYTE MZ01-CE1-00/MZ01-CE1-00, BIOS F02 08/29/2018
[ 483.601229] Call Trace:
[ 483.603768] dump_stack+0x6d/0x89
[ 483.607221] kvm_vcpu_gfn_to_memslot+0x168/0x170 [kvm]
[ 483.612567] kvm_vcpu_unmap+0x28/0x60 [kvm]
[ 483.616953] pre_sev_run+0x122/0x250 [kvm_amd]
[ 483.621546] svm_vcpu_run+0x50d/0x780 [kvm_amd]
[ 483.626227] kvm_arch_vcpu_ioctl_run+0xe36/0x1bd0 [kvm]
[ 483.631682] ? kvm_arch_vcpu_ioctl_run+0xc2/0x1bd0 [kvm]
[ 483.637233] ? lock_is_held_type+0xd1/0x130
[ 483.641563] kvm_vcpu_ioctl+0x222/0x650 [kvm]
[ 483.646127] ? __fget_files+0xe3/0x190
[ 483.650005] ? __fget_files+0x5/0x190
[ 483.653806] __x64_sys_ioctl+0x98/0xd0
[ 483.657693] ? lockdep_hardirqs_on+0x88/0x120
[ 483.662193] do_syscall_64+0x41/0x80
[ 483.665902] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 483.671100] RIP: 0033:0x7fde49a2f457
[ 483.674809] Code: 00 00 90 48 8b 05 39 7a 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 09 7a 0c 00 f7 d8 64 89 01 48
[ 483.693875] RSP: 002b:00007fde461547e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[ 483.701631] RAX: ffffffffffffffda RBX: 000000000000ae80 RCX: 00007fde49a2f457
[ 483.708919] RDX: 0000000000000000 RSI: 000000000000ae80 RDI: 0000000000000015
[ 483.716207] RBP: 00005615a1bf8500 R08: 00005615a00ee278 R09: 00000000ffffffff
[ 483.723496] R10: 0000000000000001 R11: 0000000000000246 R12: 0000000000000000
[ 483.730787] R13: 00007fde4a37d004 R14: 0000000000000cf8 R15: 0000000000000000
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
reply other threads:[~2021-05-04 10:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YJEbzVjirlgscmLU@zn.tnic \
--to=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.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