Re: printk() with a spin-lock held.

From: Richard B. Johnson
Date: Mon Oct 25 2004 - 07:34:48 EST


On Fri, 22 Oct 2004, Lee Revell wrote:

On Fri, 2004-10-22 at 15:07 -0400, Richard B. Johnson wrote:
Linux-2.6.9 will bug-check and halt if my code executes
a printk() with a spin-lock held.

Is this the intended behavior?

Yes. printk() can sleep. No sleeping with a spinlock held.

If so, NotGood(tm).

See above. If you think you can improve the situation, patches are
welcome, as always.

Lee


I recall that printk() useds to just write stuff into a buffer,
that the buffer (the same buffer used for dmesg), was written
out only when it was safe to do so.


Now, if printk() can't do that anymore, how does one de-bug
ISR code? Or do you just heave it off the cliff and hope that
it flies?


Cheers,
Dick Johnson
Penguin : Linux version 2.6.9 on an i686 machine (5537.79 GrumpyMips).
98.36% of all statistics are fiction.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/