From: Andrew Morton <akpm@linux-foundation.org>
To: Ming Lei <ming.lei@canonical.com>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-pm@vger.kernel.org,
linux-mm@kvack.org, Alan Stern <stern@rowland.harvard.edu>,
Oliver Neukum <oneukum@suse.de>, Minchan Kim <minchan@kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Jens Axboe <axboe@kernel.dk>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v7 0/6] solve deadlock caused by memory allocation with I/O
Date: Wed, 16 Jan 2013 15:37:44 -0800 [thread overview]
Message-ID: <20130116153744.70210fa3.akpm@linux-foundation.org> (raw)
In-Reply-To: <1357352744-8138-1-git-send-email-ming.lei@canonical.com>
On Sat, 5 Jan 2013 10:25:38 +0800
Ming Lei <ming.lei@canonical.com> wrote:
> This patchset try to solve one deadlock problem which might be caused
> by memory allocation with block I/O during runtime PM and block device
> error handling path. Traditionly, the problem is addressed by passing
> GFP_NOIO statically to mm, but that is not a effective solution, see
> detailed description in patch 1's commit log.
>
> This patch set introduces one process flag and trys to fix the deadlock
> problem on block device/network device during runtime PM or usb bus reset.
The patchset doesn't look like the worst thing I've ever applied ;)
One thing I'm wondering: during suspend and resume, why are GFP_KERNEL
allocation attempts even getting down to the device layer? Presumably
the page scanner is encountering dirty pagecache or dirty swapcache
pages?
If so, I wonder if we could avoid the whole problem by appropriately
syncing all dirty memory back to storage before starting to turn devices
off?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-01-16 23:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 2:25 [PATCH v7 0/6] solve deadlock caused by memory allocation with I/O Ming Lei
2013-01-05 2:25 ` [PATCH v7 1/6] mm: teach mm by current context info to not do I/O during memory allocation Ming Lei
2013-01-05 2:25 ` [PATCH v7 2/6] PM / Runtime: introduce pm_runtime_set_memalloc_noio() Ming Lei
2013-01-05 2:25 ` [PATCH v7 3/6] block/genhd.c: apply pm_runtime_set_memalloc_noio on block devices Ming Lei
2013-01-05 2:25 ` [PATCH v7 4/6] net/core: apply pm_runtime_set_memalloc_noio on network devices Ming Lei
2013-01-05 2:25 ` [PATCH v7 5/6] PM / Runtime: force memory allocation with no I/O during Runtime PM callbcack Ming Lei
2013-01-05 2:25 ` [PATCH v7 6/6] USB: forbid memory allocation with I/O during bus reset Ming Lei
2013-01-16 23:37 ` Andrew Morton [this message]
2013-01-17 1:28 ` [PATCH v7 0/6] solve deadlock caused by memory allocation with I/O Ming Lei
2013-01-17 9:44 ` Oliver Neukum
2013-01-17 21:57 ` Andrew Morton
2013-01-18 10:22 ` 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=20130116153744.70210fa3.akpm@linux-foundation.org \
--to=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=oneukum@suse.de \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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).