Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH] NVMe: Fix abort handling
Date: Mon, 08 Dec 2014 12:18:42 -0700	[thread overview]
Message-ID: <5485F992.7010000@kernel.dk> (raw)
In-Reply-To: <5485FA49.8020707@micron.com>

On 12/08/2014 12:21 PM, Sam Bradshaw wrote:
> This patch fixes some problems in the abort handling code; freeing the
> correct request (abort_req) and setting abort_limit & rq_aborted if
> submitted the abort request fails.  In addition, a device reset is
> scheduled pro-actively if the device fails to successful abort a command
> rather than waiting for the timeout handler to disposition the condition.

Generally I'm not a huge fan of patches that end up having "in addition" 
or "additionally" in the commit message, that's usually a clear sign 
that it should have been two (or more) patches.

I'll cut this hunk:

> @@ -1054,7 +1066,9 @@ static void nvme_abort_req(struct request *req)
>   		dev_warn(nvmeq->q_dmadev,
>   				"Could not abort I/O %d QID %d",
>   				req->tag, nvmeq->qid);
> -		blk_mq_free_request(req);
> +		blk_mq_free_request(abort_req);
> +		++dev->abort_limit;
> +		cmd_rq->aborted = 0;
>   	}
>   }

since that's a clear bug fix, and you can hash out the details on the 
reset handling with Keith, since he's a lot more qualified to render an 
opinion on that.

OK?

-- 
Jens Axboe

      parent reply	other threads:[~2014-12-08 19:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 19:21 [PATCH] NVMe: Fix abort handling Sam Bradshaw
2014-12-08 19:16 ` Keith Busch
2014-12-08 19:18 ` 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=5485F992.7010000@kernel.dk \
    --to=axboe@kernel.dk \
    /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