[vbox-dev] vbox kernel modules cause hardlock on kernel 4.2.0-rc2
ramshankar.venkataraman at oracle.com
Fri Jul 17 09:13:44 GMT 2015
On 07/16/2015 06:15 PM, Ramshankar wrote:
> Oops, misread your original report. It *is* the WARN panic. I'll try to
> provide a test build soon to fix this issue.
Please let me know if this build works works for you:
>> I'm not sure how that is happening.
>> This changeset
>> reverts to the old assumptions of the caller disabling preemption while
>> calling preempt_notifier_register()/preempt_notifier_unregister().
>> We would get into the "slower" path but i don't think that should really
>> cause the kernel panic like before.
>> We would need to call the newly introduced functions
>> preempt_notifier_inc() and preempt_notifier_dec() but that should be a
>> performance issue and not a fatal panic afaict unless "WARN" ends up
>> panicking the system in which case it should be a different panic and
>> not the original oops you posted.
>> vbox-dev mailing list
>> vbox-dev at virtualbox.org
> vbox-dev mailing list
> vbox-dev at virtualbox.org
More information about the vbox-dev