From: Alan Stern <stern@rowland.harvard.edu>
To: Ming Lei <ming.lei@canonical.com>
Cc: Oliver Neukum <oneukum@suse.de>, <linux-kernel@vger.kernel.org>,
Minchan Kim <minchan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Jens Axboe <axboe@kernel.dk>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
<netdev@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<linux-pm@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH v3 2/6] PM / Runtime: introduce pm_runtime_set[get]_memalloc_noio()
Date: Wed, 31 Oct 2012 11:20:02 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1210311117310.1954-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <CACVXFVNxucCVLS-=EQkmVop3LQMkeXW7RbZq4yfkiq_MUGndvg@mail.gmail.com>
On Wed, 31 Oct 2012, Ming Lei wrote:
> The below idea may help the problem which 'memalloc_noio' flag isn't set during
> usb_reset_device().
>
> - for usb mass storage device, call pm_runtime_set_memalloc_noio(true)
> inside usb_stor_probe2() and uas_probe(), and call
> pm_runtime_set_memalloc_noio(false) inside uas_disconnect()
> and usb_stor_disconnect().
Why would you want to do that? The probe and disconnect routines
usually -- but not always -- run in the khubd thread. Surely you don't
want to prevent khubd from using GFP_KERNEL?
And what if probe runs in khubd but disconnect runs in a different
thread?
Alan Stern
next prev parent reply other threads:[~2012-10-31 15:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 12:23 [PATCH v3 0/6] solve deadlock caused by memory allocation with I/O Ming Lei
2012-10-29 12:23 ` [PATCH v3 1/6] mm: teach mm by current context info to not do I/O during memory allocation Ming Lei
2012-10-29 12:23 ` [PATCH v3 2/6] PM / Runtime: introduce pm_runtime_set[get]_memalloc_noio() Ming Lei
2012-10-29 15:41 ` Alan Stern
2012-10-30 3:21 ` Ming Lei
2012-10-30 10:57 ` Oliver Neukum
2012-10-30 11:30 ` Ming Lei
2012-10-30 15:38 ` Alan Stern
2012-10-30 16:00 ` Ming Lei
2012-10-30 16:15 ` Ming Lei
2012-10-30 16:30 ` Oliver Neukum
2012-10-31 2:08 ` Ming Lei
2012-10-31 3:05 ` Ming Lei
2012-10-31 8:37 ` Oliver Neukum
2012-10-31 15:20 ` Alan Stern [this message]
2012-10-31 15:41 ` Alan Stern
2012-10-31 23:18 ` Ming Lei
2012-10-30 16:54 ` Alan Stern
2012-10-29 12:23 ` [PATCH v3 3/6] block/genhd.c: apply pm_runtime_set_memalloc_noio on block devices Ming Lei
2012-10-29 12:23 ` [PATCH v3 4/6] net/core: apply pm_runtime_set_memalloc_noio on network devices Ming Lei
2012-10-29 15:44 ` Alan Stern
2012-10-29 12:23 ` [PATCH v3 5/6] PM / Runtime: force memory allocation with no I/O during runtime_resume callbcack Ming Lei
2012-10-29 12:24 ` [PATCH v3 6/6] USB: forbid memory allocation with I/O during bus reset Ming Lei
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=Pine.LNX.4.44L0.1210311117310.1954-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ming.lei@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=rjw@sisk.pl \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).