Messages in this thread | | | Date | Sun, 2 Jul 2000 03:02:08 -0500 (CDT) | From | Jeff Garzik <> | Subject | Re: [PATCH #2] console lock grabbed too early in printk... |
| |
On Sun, 2 Jul 2000, Chris Lattner wrote: > Like I said a few times already... kmalloc is only called in a situation > where deadlock would occur before... I would have no problem calling it > with GFP_ATOMIC and dropping the message if OOM...
-Is- a deadlock occurring for you, or others, though? If so, we had better find the problem and fix it before dicking around with making printk prettier and faster.
I thought this thread was about reducing the time that console_lock had to be held...
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |