> Thanks for this hint. So this means kmalloc(GFP_KERNEL) inside
> spinlock is not necessarily dangerous, but should be avoided if
> possible? Is using a semaphore better than using spinlocks? Is
> there a list of dos and don'ts for preempt kernels beside
> Documentation/preempt-locking.txt?
>
> And btw, who is "us"?
The Cab^Kernel developers ;)
-- function.linuxpower.ca- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/