Robert Love wrote:
> On Tue, 2002-07-09 at 14:00, William Lee Irwin III wrote:
>
>
>>This is an ugly aspect. But AFAICT the most that's needed to clean it
>>up is an explicit release before potentially sleeping.
>
>
> Yep that is all we need... remove the release_kernel_lock() and
> reacquire_kernel_lock() from schedule and do it explicitly everywhere it
> is needed.
>
> The problem is, it is needed in a _lot_ of places. Mostly instances
> where the lock is held across something that may implicitly sleep.
And _that_ is why I wrote the BKL debugging patch, to help find these
places at runtime. It may not be pretty, but it works. I'll post it
again if you're interested.
-- Dave Hansen haveblue@us.ibm.com- 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/
This archive was generated by hypermail 2b29 : Mon Jul 15 2002 - 22:00:16 EST