From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <tom.leiming@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] blk-mq: fix schedule from atomic context
Date: Mon, 02 Jun 2014 09:19:55 -0600 [thread overview]
Message-ID: <538C961B.6070605@kernel.dk> (raw)
In-Reply-To: <1401554617-10099-3-git-send-email-tom.leiming@gmail.com>
On 2014-05-31 10:43, Ming Lei wrote:
> blk_mq_put_ctx() has to be called before io_schedule() in
> bt_get().
>
> This patch fixes the problem by taking similar approach from
> percpu_ida allocation for the situation.
Thanks, I've applied these to for post-merge integration. I do think we
can clean up further around 'data' for bt_get(), for instance, and
possibly in other places too.
--
Jens Axboe
prev parent reply other threads:[~2014-06-02 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-31 16:43 [PATCH 0/2] blk-mq: fix schedule from atomic context Ming Lei
2014-05-31 16:43 ` [PATCH 1/2] blk-mq: move blk_mq_get_ctx/blk_mq_put_ctx to mq private header Ming Lei
2014-05-31 16:43 ` [PATCH 2/2] blk-mq: fix schedule from atomic context Ming Lei
2014-06-02 15:19 ` Jens Axboe [this message]
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=538C961B.6070605@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.