From: Dan Williams <dan.j.williams@intel.com>
To: Shaohua Li <shli@kernel.org>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"neilb@suse.de" <neilb@suse.de>
Subject: Re: [RFC]md: using GFP_NOIO to allocate bio for flush request
Date: Tue, 8 May 2012 12:31:18 -0700 [thread overview]
Message-ID: <CAA9_cmc4eT=uwXNdupkxK9_NWW4TLVab5-NBojL9PydHs73zfA@mail.gmail.com> (raw)
In-Reply-To: <20120508101800.GB9757@kernel.org>
On Tue, May 8, 2012 at 3:18 AM, Shaohua Li <shli@kernel.org> wrote:
> On Mon, Apr 16, 2012 at 01:32:06PM +0800, Shaohua Li wrote:
>>
>> flush request is issued in transaction commit code path usually, so
>> looks using
>> GFP_KERNEL to allocate memory for flush request bio falls into the classic
>> deadlock issue. dm already gets it right.
> ping!
>
This one should probably also be queued for -stable right?
next prev parent reply other threads:[~2012-05-08 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 5:32 [RFC]md: using GFP_NOIO to allocate bio for flush request Shaohua Li
2012-05-08 10:18 ` Shaohua Li
2012-05-08 19:31 ` Dan Williams [this message]
2012-05-08 20:14 ` NeilBrown
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='CAA9_cmc4eT=uwXNdupkxK9_NWW4TLVab5-NBojL9PydHs73zfA@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=shli@kernel.org \
/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).