Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2992735AbXBQRHN (ORCPT ); Sat, 17 Feb 2007 12:07:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S2992479AbXBQQ6F (ORCPT ); Sat, 17 Feb 2007 11:58:05 -0500 Received: from firewall.rowland.harvard.edu ([140.247.233.35]:9324 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with SMTP id S2992475AbXBQQ56 (ORCPT ); Sat, 17 Feb 2007 11:57:58 -0500 Date: Sat, 17 Feb 2007 11:57:55 -0500 (EST) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: Dan Aloni cc: Linux Kernel List , Subject: Re: [linux-usb-devel] OOM and USB, latest Linux 2.6 In-Reply-To: <20070217164920.GA31755@localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 742 Lines: 22 On Sat, 17 Feb 2007, Dan Aloni wrote: > Hello, > > Is it possible that OOM isn't handled very well if say, my entire > file system structure is on a USB storage device? > > I'm not an expert on this particular matter but I'm pretty sure > that I noticed GFP_KERNEL allocation being done on the write-out > path in the usb-storage kernel thread, leading to a deadlock > during OOM. Can you be any more specific than that? usb-storage should use only GFP_NOIO in its I/O paths. Alan Stern - 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/