Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263798AbTEMXT7 (ORCPT ); Tue, 13 May 2003 19:19:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263800AbTEMXT7 (ORCPT ); Tue, 13 May 2003 19:19:59 -0400 Received: from pc2-cwma1-4-cust86.swan.cable.ntl.com ([213.105.254.86]:12447 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S263798AbTEMXT6 (ORCPT ); Tue, 13 May 2003 19:19:58 -0400 Subject: Re: [patch] 2.4 fix to allow vmalloc at interrupt time From: Alan Cox To: mjacob@quaver.net Cc: Linux Kernel Mailing List In-Reply-To: <20030513140629.I83125@mailhost.quaver.net> References: <20030512225654.GA27358@cm.nu> <20030513140629.I83125@mailhost.quaver.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1052865254.1205.7.camel@dhcp22.swansea.linux.org.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 13 May 2003 23:34:15 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 710 Lines: 17 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/