Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
Subject: [GIT PULL] nvme fixes for 4.18
Date: Fri, 15 Jun 2018 15:13:01 +0200	[thread overview]
Message-ID: <20180615131301.2teay6o7c2jrqxtw@infradead.org> (raw)

Fix various little regressions introduced in this merge window, plus
a rework of the fibre channel connect and reconnect path to share the
code instead of having separate sets of bugs.  Last but not least a
trivial trace point addition from Hannes.


The following changes since commit 190b02ed79e08983bf62d47c05945c1b06a3d7d5:

  block: fix use-after-free in block flush handling (2018-06-09 06:37:14 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git nvme-4.18

for you to fetch changes up to 35897b920c8ab5e23331ad429e0aa235528c63ba:

  nvme-fabrics: fix and refine state checks in __nvmf_check_ready (2018-06-15 11:21:00 +0200)

----------------------------------------------------------------
Chaitanya Kulkarni (1):
      nvmet: free smart-log buffer after use

Christoph Hellwig (6):
      nvme: don't rely on the changed namespace list log
      nvme: remove nvme_reinit_tagset
      blk-mq: remove blk_mq_tagset_iter
      nvme-fabrics: refactor queue ready check
      nvme-fabrics: handle the admin-only case properly in nvmf_check_ready
      nvme-fabrics: fix and refine state checks in __nvmf_check_ready

Hannes Reinecke (1):
      nvme: add bio remapping tracepoint

Israel Rukshin (1):
      nvme: fix NULL pointer dereference in nvme_init_subsystem

James Smart (3):
      nvme-fc: change controllers first connect to use reconnect path
      nvme-fc: remove reinit_request routine
      nvme-fc: fix nulling of queue data on reconnect

Max Gurtovoy (1):
      nvme-rdma: fix error flow during mapping request data

 block/blk-mq-tag.c              |  29 --------
 drivers/nvme/host/core.c        |  48 ++++----------
 drivers/nvme/host/fabrics.c     |  86 +++++++++++-------------
 drivers/nvme/host/fabrics.h     |  14 +++-
 drivers/nvme/host/fc.c          | 144 ++++++++++++++++------------------------
 drivers/nvme/host/multipath.c   |   4 ++
 drivers/nvme/host/nvme.h        |   2 -
 drivers/nvme/host/rdma.c        |  38 ++++++++---
 drivers/nvme/target/admin-cmd.c |   4 +-
 drivers/nvme/target/loop.c      |   7 +-
 include/linux/blk-mq.h          |   2 -
 11 files changed, 154 insertions(+), 224 deletions(-)

             reply	other threads:[~2018-06-15 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 13:13 Christoph Hellwig [this message]
2018-06-15 14:16 ` [GIT PULL] nvme fixes for 4.18 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2018-07-26 14:16 Christoph Hellwig
2018-07-26 17:49 ` Jens Axboe
2018-06-22 13:00 Christoph Hellwig
2018-06-22 14:46 ` Jens Axboe
2018-06-08  5:58 Christoph Hellwig
2018-06-08 13:09 ` Jens Axboe
2018-06-08 18:51   ` 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=20180615131301.2teay6o7c2jrqxtw@infradead.org \
    --to=hch@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