![]() | ||||||||||
Messages in this thread |
> Actually it already does, to cover the case where an interrupt handler calls > printk while process-context code is performing a printk. I don't think it'll work. Both printk and release_console_sem take the logbuf_lock, which will deadlock if the same CPU already holds it. It would need to use the usual linux recursive lock hack. -Andi - 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/ | |||||||||
| Last update: 2005-03-22 12:36 [from the cache] ©2003-2008 | ||||||||||