Subject: Re: [patch] 2.4 fix to allow vmalloc at interrupt time
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: mjacob@quaver.net
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
In-Reply-To: <1052865254.1205.7.camel@dhcp22.swansea.linux.org.uk>
References: <20030512225654.GA27358@cm.nu>
	 <20030513140629.I83125@mailhost.quaver.net>
	 <1052865254.1205.7.camel@dhcp22.swansea.linux.org.uk>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: 
Message-Id: <1052868103.1206.28.camel@dhcp22.swansea.linux.org.uk>
Mime-Version: 1.0
Date: 14 May 2003 00:21:45 +0100
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 828
Lines: 19

On Maw, 2003-05-13 at 23:34, Alan Cox wrote:
> 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.

problems even. 1am isnt the best time for posting ;)

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