> Ahhah! I know. You just make lock_depth 0 when you exit, without actually
> taking the kernel lock. Which fools the logic into accepting a
> preempt-disable, since it thinks that the preempt disable is due to
> holding the kernel lock.
I was this -> <- close to celebrating. Not so fast, smarty.
What about release_kernel_lock() ?
It sees task->lock_depth>=0 and calls spin_unlock() on a lock that it
does not hold.
Robert Love
-
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/