Re: [patch] 2.4 fix to allow vmalloc at interrupt time

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Tue May 13 2003 - 17:34:15 EST

Next message: Joel Becker: "Re: 2.5.69-mm4 fails to boot"
Previous message: William Lee Irwin III: "Re: Race between vmtruncate and mapped areas?"
In reply to: Matthew Jacob: "[patch] 2.4 fix to allow vmalloc at interrupt time"
Next in thread: Alan Cox: "Re: [patch] 2.4 fix to allow vmalloc at interrupt time"
Reply: Alan Cox: "Re: [patch] 2.4 fix to allow vmalloc at interrupt time"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Maw, 2003-05-13 at 22:11, Matthew Jacob wrote:
> This fixes a buglet wrt doing vmalloc at interrupt time for 2.4.
>
> get_vm_area should call kmalloc with GFP_ATOMIC- after all, it's
> set up to allow for an allocation failure. As best as I read
> the 2.4 code, the rest of the path through _kmem_cache_alloc
> should be safe.

You aren't allow to vmalloc in an IRQ. The kmalloc is the least of
your programs - you have to worry about the page table handling.

-
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/

Next message: Joel Becker: "Re: 2.5.69-mm4 fails to boot"
Previous message: William Lee Irwin III: "Re: Race between vmtruncate and mapped areas?"
In reply to: Matthew Jacob: "[patch] 2.4 fix to allow vmalloc at interrupt time"
Next in thread: Alan Cox: "Re: [patch] 2.4 fix to allow vmalloc at interrupt time"
Reply: Alan Cox: "Re: [patch] 2.4 fix to allow vmalloc at interrupt time"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu May 15 2003 - 22:00:49 EST