Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 25 Aug 2002 22:00:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 25 Aug 2002 22:00:13 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:26898 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id ; Sun, 25 Aug 2002 22:00:12 -0400 Message-ID: <3D698F4E.93A3DDA2@zip.com.au> Date: Sun, 25 Aug 2002 19:15:42 -0700 From: Andrew Morton X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.19-rc5 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Martin J. Bligh" CC: Steven Cole , lkml , "linux-mm@kvack.org" Subject: Re: MM patches against 2.5.31 References: <1030031958.14756.479.camel@spc9.esa.lanl.gov> <2631076918.1030007179@[10.10.2.3]> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 836 Lines: 23 "Martin J. Bligh" wrote: > > > kjournald: page allocation failure. order:0, mode:0x0 > > I've seen this before, but am curious how we ever passed > a gfpmask (aka mode) of 0 to __alloc_pages? Can't see anywhere > that does this? Could be anywhere, really. A network interrupt doing GFP_ATOMIC while kjournald is executing. A radix-tree node allocation on the add-to-swap path perhaps. (The swapout failure messages aren't supposed to come out, but mempool_alloc() stomps on the caller's setting of PF_NOWARN.) Or: mnm:/usr/src/25> grep -r GFP_ATOMIC drivers/scsi/*.c | wc -l 89 - 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/