DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=nFaiJ040FrisoG+M6yJp3hAggZbr2s/2zpyM4IPdOtEv9zsEg9SF8iwidRQldQugtUCk+wagXZUz0dEutUXm1asqsLjWhjYAab5/QtSzIoIw0Pwm0tHJqnO/zcnK3nxL4FtY3jXm4gEnOvlqYt8V76BMaoorcxXcuOEjQOr2n6E=  ;
Message-ID: <20061023111145.52479.qmail@web32412.mail.mud.yahoo.com>
Date: Mon, 23 Oct 2006 04:11:45 -0700 (PDT)
From: Giridhar Pemmasani <pgiri@yahoo.com>
Subject: Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <1161599894.19388.11.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 955
Lines: 26

--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> You are not allowed to call vmalloc in atomic context, especially in
> interrupt paths. Vmalloc has to do TLB handling work and that can
> involve cross calls and other stuff that isn't IRQ friendly on all
> platforms.

This has been discussed before:

http://marc.theaimsgroup.com/?l=linux-kernel&m=114831100404677&w=2

The problem is not with calling vmalloc in atomic context, but __vmalloc,
which can be. The proposed patch makes sure __vmalloc is not supposed to be
called in interrupt context.

Giri

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-
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/