Messages in this thread | | | Date | Sun, 2 Jul 2000 00:25:16 -0700 (PDT) | From | Chris Lattner <> | Subject | Re: [PATCH #2] console lock grabbed too early in printk... |
| |
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...
-Chris
On Sat, 1 Jul 2000, Philipp Rumpf wrote:
> On Sat, Jul 01, 2000 at 09:54:36PM -0500, Jeff Garzik wrote: > > I'm not even sure that kmalloc during printk is possible, since > > printk might be called during kernel init, before all the kmem caches > > are created. (have no kernel tree here to check this, alas) > > It definitely can be called early, and it should be possible to call it in > OOM situations and out of kmalloc(). Using kmalloc in printk() isn't > acceptable. >
- 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/
| |