All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>,
	Keith Busch <keith.busch@intel.com>
Subject: [GIT PULL] nvme fixes for the next round of 5.3-rc
Date: Fri,  9 Aug 2019 11:04:12 -0700	[thread overview]
Message-ID: <20190809180412.26392-1-sagi@grimberg.me> (raw)

Hey Jens,

Few nvme fixes for the next rc round.
- detect capacity changes on the mpath disk from Anthony
- probe/remove fix from Keith
- various fixes to pass blktests from Logan
- deadlock in reset/scan race fix
- nvme-rdma use-after-free fix
- deadlock fix when passthru commands race mpath disk info update

The following changes since commit 71d6c505b4d9e6f76586350450e785e3d452b346:

  libata: zpodd: Fix small read overflow in zpodd_get_mech_type() (2019-07-29 16:00:14 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git nvme-5.3-rc 

for you to fetch changes up to bd46a90634302bfe791e93ad5496f98f165f7ae0:

  nvme-pci: Fix async probe remove race (2019-07-31 18:03:36 -0700)

----------------------------------------------------------------
Anthony Iliopoulos (1):
      nvme-multipath: revalidate nvme_ns_head gendisk in nvme_validate_ns

Keith Busch (1):
      nvme-pci: Fix async probe remove race

Logan Gunthorpe (4):
      nvmet: Fix use-after-free bug when a port is removed
      nvmet-loop: Flush nvme_delete_wq when removing the port
      nvmet-file: fix nvmet_file_flush() always returning an error
      nvme-core: Fix extra device_put() call on error path

Sagi Grimberg (3):
      nvme: fix a possible deadlock when passthru commands sent to a multipath device
      nvme-rdma: fix possible use-after-free in connect error flow
      nvme: fix controller removal race with scan work

 drivers/nvme/host/core.c       | 15 ++++++++-
 drivers/nvme/host/multipath.c  | 76 ++++++++++++++++++++++++++++++++++++++----
 drivers/nvme/host/nvme.h       | 21 ++++++++++--
 drivers/nvme/host/pci.c        |  3 +-
 drivers/nvme/host/rdma.c       | 16 ++++++---
 drivers/nvme/target/configfs.c |  1 +
 drivers/nvme/target/core.c     | 15 +++++++++
 drivers/nvme/target/loop.c     |  8 +++++
 drivers/nvme/target/nvmet.h    |  3 ++
 9 files changed, 143 insertions(+), 15 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: sagi@grimberg.me (Sagi Grimberg)
Subject: [GIT PULL] nvme fixes for the next round of 5.3-rc
Date: Fri,  9 Aug 2019 11:04:12 -0700	[thread overview]
Message-ID: <20190809180412.26392-1-sagi@grimberg.me> (raw)

Hey Jens,

Few nvme fixes for the next rc round.
- detect capacity changes on the mpath disk from Anthony
- probe/remove fix from Keith
- various fixes to pass blktests from Logan
- deadlock in reset/scan race fix
- nvme-rdma use-after-free fix
- deadlock fix when passthru commands race mpath disk info update

The following changes since commit 71d6c505b4d9e6f76586350450e785e3d452b346:

  libata: zpodd: Fix small read overflow in zpodd_get_mech_type() (2019-07-29 16:00:14 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git nvme-5.3-rc 

for you to fetch changes up to bd46a90634302bfe791e93ad5496f98f165f7ae0:

  nvme-pci: Fix async probe remove race (2019-07-31 18:03:36 -0700)

----------------------------------------------------------------
Anthony Iliopoulos (1):
      nvme-multipath: revalidate nvme_ns_head gendisk in nvme_validate_ns

Keith Busch (1):
      nvme-pci: Fix async probe remove race

Logan Gunthorpe (4):
      nvmet: Fix use-after-free bug when a port is removed
      nvmet-loop: Flush nvme_delete_wq when removing the port
      nvmet-file: fix nvmet_file_flush() always returning an error
      nvme-core: Fix extra device_put() call on error path

Sagi Grimberg (3):
      nvme: fix a possible deadlock when passthru commands sent to a multipath device
      nvme-rdma: fix possible use-after-free in connect error flow
      nvme: fix controller removal race with scan work

 drivers/nvme/host/core.c       | 15 ++++++++-
 drivers/nvme/host/multipath.c  | 76 ++++++++++++++++++++++++++++++++++++++----
 drivers/nvme/host/nvme.h       | 21 ++++++++++--
 drivers/nvme/host/pci.c        |  3 +-
 drivers/nvme/host/rdma.c       | 16 ++++++---
 drivers/nvme/target/configfs.c |  1 +
 drivers/nvme/target/core.c     | 15 +++++++++
 drivers/nvme/target/loop.c     |  8 +++++
 drivers/nvme/target/nvmet.h    |  3 ++
 9 files changed, 143 insertions(+), 15 deletions(-)

             reply	other threads:[~2019-08-09 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 18:04 Sagi Grimberg [this message]
2019-08-09 18:04 ` [GIT PULL] nvme fixes for the next round of 5.3-rc Sagi Grimberg
2019-08-11  3:42 ` Jens Axboe
2019-08-11  3:42   ` 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=20190809180412.26392-1-sagi@grimberg.me \
    --to=sagi@grimberg.me \
    --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 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.