From: Larry Finger <Larry.Finger@lwfinger.net>
To: Peter Zijlstra <peterz@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Kernel crashes in VirtualBox module after commit 2ecd9d29abb1
Date: Mon, 10 Aug 2015 16:49:49 -0500 [thread overview]
Message-ID: <55C91C7D.2020506@lwfinger.net> (raw)
A problem with the VirtualBox kernel module vboxdrv.ko has been bisected to
commit 2ecd9d29abb1 "sched, preempt_notifier: separate notifier registration
from static_key inc/dec". The affected kernels crash is various ways. The most
instructive includes a warning issued at kernel/sched/core.c:2342 in
prempt_notifier_register() for "registering prempt_notifier while notifiers
disabled" The call from vboxdrv is as follows:
/*
* Register the callback.
*/
preempt_disable();
pThis->fEnabled = true;
preempt_notifier_register(&pThis->LnxPreemptNotifier);
preempt_enable();
As I have no reason to suspect the kernel after this patch, I would like some
suggestions regarding the best method to patch/fix the VirtualBox code.
Thanks,
Larry
next reply other threads:[~2015-08-10 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 21:49 Larry Finger [this message]
2015-08-11 7:44 ` Kernel crashes in VirtualBox module after commit 2ecd9d29abb1 Peter Zijlstra
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=55C91C7D.2020506@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox