From: Josef Bacik <josef@toxicpanda.com>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@kernel.dk, keith.busch@intel.com, josef@toxicpanda.com,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] blk-mq: only iterate over inflight requests in blk_mq_tagset_busy_iter
Date: Wed, 30 May 2018 13:27:32 -0400 [thread overview]
Message-ID: <20180530172731.md54u3wuri3qmfbv@destiny> (raw)
In-Reply-To: <20180530165100.31186-1-hch@lst.de>
On Wed, May 30, 2018 at 06:51:00PM +0200, Christoph Hellwig wrote:
> We already check for started commands in all callbacks, but we should
> also protect against already completed commands. Do this by taking
> the checks to common code.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Josef Bacik <josef@toxicpanda.com>
for the nbd portion. Thanks,
Josef
next prev parent reply other threads:[~2018-05-30 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 16:51 [PATCH] blk-mq: only iterate over inflight requests in blk_mq_tagset_busy_iter Christoph Hellwig
2018-05-30 17:27 ` Josef Bacik [this message]
2018-05-30 17:32 ` Jens Axboe
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=20180530172731.md54u3wuri3qmfbv@destiny \
--to=josef@toxicpanda.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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