LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dan Aloni <da-x@monatomic.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
	linux-usb-devel-bounces@lists.sourceforge.net
Subject: Re: [linux-usb-devel] OOM and USB, latest Linux 2.6
Date: Sat, 17 Feb 2007 20:15:09 +0200	[thread overview]
Message-ID: <45D7462D.6080700@monatomic.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0702171156300.4173-100000@netrider.rowland.org>

Alan Stern wrote:
> 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.
>
>
>   
You are right, I looked over this state with kdb, and usb-storage
waited in usb_stor_bulk_transfer_sg, which does pass GFP_NOIO
at this scenario.

It looked suspicious though, because OOM handling was invoked
from many processes, and it didn't print about any process being
killed and it didn't complain about no processes to kill either.

(I'll look more into this, perhaps there's an OOM handling bug)

BTW, soft-rebooting the machine in that state made the USB
storage device (LEXAR,  JD LIGHTNING II) inaccessible to the
BIOS. I had to do a complete power cycle in order or the BIOS
to see it again.

-- 
Dan Aloni
XIV LTD, http://www.xivstorage.com
da-x (at) monatomic.org, dan (at) xiv.co.il


  reply	other threads:[~2007-02-17 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-17 16:49 Dan Aloni
2007-02-17 16:57 ` [linux-usb-devel] " Alan Stern
2007-02-17 18:15   ` Dan Aloni [this message]
2007-02-17 18:24     ` Dan Aloni
2007-02-17 21:36     ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45D7462D.6080700@monatomic.org \
    --to=da-x@monatomic.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel-bounces@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    --subject='Re: [linux-usb-devel] OOM and USB, latest Linux 2.6' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).