linux-kernel - Kernel crashes in VirtualBox module after commit 2ecd9d29abb1

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-next>] [day] [month] [year] [list]

Message-ID: <55C91C7D.2020506@lwfinger.net>
Date:	Mon, 10 Aug 2015 16:49:49 -0500
From:	Larry Finger <Larry.Finger@...inger.net>
To:	Peter Zijlstra <peterz@...radead.org>,
	Paolo Bonzini <pbonzini@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Kernel crashes in VirtualBox module after commit 2ecd9d29abb1

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
--
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/