| To: | Andrew Morton <akpm@xxxxxxxxx> |
|---|---|
| Subject: | Re: patch for common networking error messages |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Tue, 17 Jun 2003 09:09:57 +0200 |
| Cc: | "David S. Miller" <davem@xxxxxxxxxx>, ak@xxxxxxx, janiceg@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, stekloff@xxxxxxxxxx, girouard@xxxxxxxxxx, lkessler@xxxxxxxxxx, kenistonj@xxxxxxxxxx, jgarzik@xxxxxxxxx |
| In-reply-to: | <20030616152707.58da808c.akpm@digeo.com> |
| References: | <3EEE28DE.6040808@us.ibm.com> <20030616.133841.35533284.davem@redhat.com> <20030616205342.GH30400@wotan.suse.de> <20030616.135124.71580008.davem@redhat.com> <20030616152707.58da808c.akpm@digeo.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
> 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 |
| Previous by Date: | Re: patch for common networking error messages, Valdis . Kletnieks |
|---|---|
| Next by Date: | Compiling linux kernel with TCP/IP debug option ON, Aamir Shafi |
| Previous by Thread: | Re: patch for common networking error messages, David S. Miller |
| Next by Thread: | Re: patch for common networking error messages, Andrew Morton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |