From: axboe@fb.com (Jens Axboe)
Subject: [PATCH] NVMe: Fix command setup on IO retry
Date: Wed, 3 Dec 2014 19:08:46 -0700 [thread overview]
Message-ID: <547FC22E.7010609@fb.com> (raw)
In-Reply-To: <1417651633-16862-1-git-send-email-keith.busch@intel.com>
On 12/03/2014 05:07 PM, Keith Busch wrote:
> On retry, the req->special is pointing to an already setup IOD, but we
> still need to setup the command context and callback, otherwise you'll
> see false twice completed errors and leak requests.
Good catch!
I'll queue this up for 3.19.
--
Jens Axboe
prev parent reply other threads:[~2014-12-04 2:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 0:07 [PATCH] NVMe: Fix command setup on IO retry Keith Busch
2014-12-04 2:08 ` 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=547FC22E.7010609@fb.com \
--to=axboe@fb.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.