sched: improve preempt debugging
This patch helped me out with a problem I recently had.... Basically, when the kernel lock is held, then preempt_count underflow does not get detected until it is released which may be a long time (and arbitrarily, eg at different points it may be rescheduled). If the bkl is released at schedule, the resulting output is actually fairly cryptic... With any other lock that elevates preempt_count, it is illegal to schedule under it (which would get found pretty quickly). bkl allows scheduling with preempt_count elevated, which makes underflows hard to debug. Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
parent
6918bc5c83
commit
7317d7b87e
1 changed files with 1 additions and 1 deletions
|
@ -4305,7 +4305,7 @@ void __kprobes sub_preempt_count(int val)
|
||||||
/*
|
/*
|
||||||
* Underflow?
|
* Underflow?
|
||||||
*/
|
*/
|
||||||
if (DEBUG_LOCKS_WARN_ON(val > preempt_count()))
|
if (DEBUG_LOCKS_WARN_ON(val > preempt_count() - (!!kernel_locked())))
|
||||||
return;
|
return;
|
||||||
/*
|
/*
|
||||||
* Is the spinlock portion underflowing?
|
* Is the spinlock portion underflowing?
|
||||||
|
|
Loading…
Reference in a new issue