All of lore.kernel.org
 help / color / mirror / Atom feed
From: axboe@kernel.dk (Jens Axboe)
Subject: NVMe IO error due to abort..
Date: Fri, 24 Feb 2017 15:12:32 -0700	[thread overview]
Message-ID: <38e75ee9-e20a-3a64-c570-c780cb593958@kernel.dk> (raw)
In-Reply-To: <CA+55aFw8=Xh=GS0KJzYKcV612EtWOvCMkfZe7H3vGT8W7AYmwQ@mail.gmail.com>

On 02/24/2017 02:55 PM, Linus Torvalds wrote:
> On Fri, Feb 24, 2017@1:35 PM, Jens Axboe <axboe@kernel.dk> wrote:
>>
>> And below is the branch info. I was going to send this in pretty soon
>> anyway, but lets see what happens.
>>
>>   git://git.kernel.dk/linux-block.git for-linus
> 
> Can you give me an overview of this all for the merge message. Might
> as well merge this properly regardless.

Yes sure, this pull request contains:

- NVMe updates and fixes that missed the first pull request. This
  includes bug fixes, and support for autonomous power management.

- Fix from Christoph for missing clear of the request payload,
  causing a problem with (at least) the storvsc driver.

- Further fixes for the queue/bdi life time issues from Jan.

- The Kconfig mq scheduler update from me.

- Fixing a use-after-free in dm-rq, spotted by Bart, introduced
  in this merge window.

- Three fixes for nbd from Josef.

- Bug fix from Omar, fixing a bug in sas transport code that
  oopses when bsg ioctls were used. From Omar.

- Improvements to the queue restart and tag wait from from
  Omar.

- Set of fixes for the sed/opal code from Scott.

- Three trivial patches to cciss from Tobin

> I'm currently just building things in a loop on the old Fedora kernel,
> just to verify stability (I had already pruned away my own 4.10 kernel
> due to the earlier "git bisect" I did on that machine due to the
> touchpad issue earlier in the merge window, so I'm using the distro
> kernel just to verify that it really isn't any new hw issue).
> 
> I'm pretty sure the hw is fine, but I'll do that a bit more, before I
> go back to current head of git for testing.
> 
> But that means I might as well just have this all already merged
> (which I do on my main desktop that has so far not shown any signs of
> this issue).

It's a puzzling issue. Let me know how it goes with the above merge, and
I can add some debug code to try and narrow this down.

-- 
Jens Axboe

  reply	other threads:[~2017-02-24 22:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 20:39 NVMe IO error due to abort Linus Torvalds
2017-02-24 20:56 ` Linus Torvalds
2017-02-24 21:02   ` Linus Torvalds
2017-02-24 21:09     ` Linus Torvalds
2017-02-24 21:16       ` Jens Axboe
2017-02-24 21:35         ` Jens Axboe
2017-02-24 21:55           ` Linus Torvalds
2017-02-24 22:12             ` Jens Axboe [this message]
2017-02-24 23:03               ` Jens Axboe
2017-02-24 23:08                 ` Linus Torvalds
2017-02-25  0:47                   ` Linus Torvalds
2017-02-25  2:44                     ` Jens Axboe
2018-02-20  9:59           ` Aurelien ROUGEMONT
2017-02-24 21:01 ` 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=38e75ee9-e20a-3a64-c570-c780cb593958@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 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.