> >Infrastructure to detect sleep-inside-spinlock bugs. Really only
> >useful if compiled with CONFIG_PREEMPT=y. It prints out a whiny
> >message and a stack backtrace if someone calls a function which might
> >sleep from within an atomic region.
> This is in my BK tree now, along with Ingo's symbolic backtraces, which
> makes it possibly less tedious to read the output.
Wheee! Thanks a LOT for merging both. We'll have lots of fun with these ones
while saving the old network protocols, that have lots of cases where we can
see problems even without these tools, imagine with them in place 8)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/