linux-kernel - Re: [linux-usb-devel] OOM and USB, latest Linux 2.6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0702171156300.4173-100000@netrider.rowland.org>
Date:	Sat, 17 Feb 2007 11:57:55 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Dan Aloni <da-x@...atomic.org>
cc:	Linux Kernel List <linux-kernel@...r.kernel.org>,
	<linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] OOM and USB, latest Linux 2.6

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/