From: Steven Rostedt <rostedt@goodmis.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: syzbot <syzbot+8d9bb6157e7b379f740e@syzkaller.appspotmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
kvm@vger.kernel.org, adrian.hunter@intel.com,
davem@davemloft.net, dedekind1@gmail.com, jbaron@redhat.com,
jpoimboe@redhat.com, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, luto@kernel.org, mingo@kernel.org,
peterz@infradead.org, richard@nod.at, riel@surriel.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: BUG: soft lockup in kvm_vm_ioctl
Date: Wed, 1 May 2019 23:10:51 -0400 [thread overview]
Message-ID: <20190501231051.50eeccd6@oasis.local.home> (raw)
In-Reply-To: <20190502023426.GA804@sol.localdomain>
On Wed, 1 May 2019 19:34:27 -0700
Eric Biggers <ebiggers@kernel.org> wrote:
> > Call Trace:
> > smp_call_function_many+0x750/0x8c0 kernel/smp.c:434
> > smp_call_function+0x42/0x90 kernel/smp.c:492
> > on_each_cpu+0x31/0x200 kernel/smp.c:602
> > text_poke_bp+0x107/0x19b arch/x86/kernel/alternative.c:821
> > __jump_label_transform+0x263/0x330 arch/x86/kernel/jump_label.c:91
> > arch_jump_label_transform+0x2b/0x40 arch/x86/kernel/jump_label.c:99
> > __jump_label_update+0x16a/0x210 kernel/jump_label.c:389
> > jump_label_update kernel/jump_label.c:752 [inline]
> > jump_label_update+0x1ce/0x3d0 kernel/jump_label.c:731
> > static_key_slow_inc_cpuslocked+0x1c1/0x250 kernel/jump_label.c:129
> > static_key_slow_inc+0x1b/0x30 kernel/jump_label.c:144
> > kvm_arch_vcpu_init+0x6b7/0x870 arch/x86/kvm/x86.c:9068
> > kvm_vcpu_init+0x272/0x370 arch/x86/kvm/../../../virt/kvm/kvm_main.c:320
> > vmx_create_vcpu+0x191/0x2540 arch/x86/kvm/vmx/vmx.c:6577
> > kvm_arch_vcpu_create+0x80/0x120 arch/x86/kvm/x86.c:8755
> > kvm_vm_ioctl_create_vcpu arch/x86/kvm/../../../virt/kvm/kvm_main.c:2569
> > [inline]
> > kvm_vm_ioctl+0x5ce/0x19c0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3105
> > vfs_ioctl fs/ioctl.c:46 [inline]
> > file_ioctl fs/ioctl.c:509 [inline]
> > do_vfs_ioctl+0xd6e/0x1390 fs/ioctl.c:696
> > ksys_ioctl+0xab/0xd0 fs/ioctl.c:713
> > __do_sys_ioctl fs/ioctl.c:720 [inline]
> > __se_sys_ioctl fs/ioctl.c:718 [inline]
> > __x64_sys_ioctl+0x73/0xb0 fs/ioctl.c:718
> > do_syscall_64+0x103/0x610 arch/x86/entry/common.c:290
> > entry_SYSCALL_64_after_hwframe+0x49/0xbe
>
> I'm also curious how syzbot found the list of people to send this to, as it
> seems very random. This should obviously have gone to the kvm mailing list, but
> it wasn't sent there; I had to manually add it.
My guess is that it went down the call stack, and picked those that
deal with the functions that are listed at the deepest part of the
stack. kvm doesn't appear for 12 functions up from the crash. It
probably stopped its search before that.
-- Steve
next prev parent reply other threads:[~2019-05-02 3:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000fb78720587d46fe9@google.com>
2019-05-02 2:34 ` BUG: soft lockup in kvm_vm_ioctl Eric Biggers
2019-05-02 3:10 ` Steven Rostedt [this message]
2019-05-08 11:23 ` Dmitry Vyukov
2019-05-08 11:25 ` Dmitry Vyukov
2019-05-08 16:58 ` Dmitry Vyukov
2019-05-09 3:18 ` Eric Biggers
2019-05-09 14:22 ` Dmitry Vyukov
2019-05-09 17:52 ` Eric Biggers
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=20190501231051.50eeccd6@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=adrian.hunter@intel.com \
--cc=davem@davemloft.net \
--cc=dedekind1@gmail.com \
--cc=dvyukov@google.com \
--cc=ebiggers@kernel.org \
--cc=jbaron@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=richard@nod.at \
--cc=riel@surriel.com \
--cc=syzbot+8d9bb6157e7b379f740e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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