All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>,
	linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for 5.10
Date: Thu, 29 Oct 2020 15:49:34 +0100	[thread overview]
Message-ID: <20201029144934.GA143642@infradead.org> (raw)

The following changes since commit f255c19b3ab46d3cad3b1b2e1036f4c926cb1d0c:

  blk-cgroup: Pre-allocate tree node on blkg_conf_prep (2020-10-26 07:57:47 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-5.10-2020-10-29

for you to fetch changes up to 3c3751f2daf6675f6b5bee83b792354c272f5bd2:

  nvmet: fix a NULL pointer dereference when tracing the flush command (2020-10-27 10:02:50 +0100)

----------------------------------------------------------------
nvme updates for 5.10:

 - improve zone revalidation (Keith Busch)
 - gracefully handle zero length messages in nvme-rdma (zhenwei pi)
 - nvme-fc error handling fixes (James Smart)
 - nvmet tracing NULL pointer dereference fix (Chaitanya Kulkarni)

----------------------------------------------------------------
Chaitanya Kulkarni (1):
      nvmet: fix a NULL pointer dereference when tracing the flush command

James Smart (4):
      nvme-fc: track error_recovery while connecting
      nvme-fc: remove err_work work item
      nvme-fc: eliminate terminate_io use by nvme_fc_error_recovery
      nvme-fc: remove nvme_fc_terminate_io()

Keith Busch (1):
      nvme: ignore zone validate errors on subsequent scans

zhenwei pi (1):
      nvme-rdma: handle unexpected nvme completion data length

 drivers/nvme/host/core.c    |   2 +-
 drivers/nvme/host/fc.c      | 270 ++++++++++++++++++--------------------------
 drivers/nvme/host/rdma.c    |   8 ++
 drivers/nvme/target/core.c  |   4 +-
 drivers/nvme/target/trace.h |  21 ++--
 5 files changed, 127 insertions(+), 178 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>,
	linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for 5.10
Date: Thu, 29 Oct 2020 15:49:34 +0100	[thread overview]
Message-ID: <20201029144934.GA143642@infradead.org> (raw)

The following changes since commit f255c19b3ab46d3cad3b1b2e1036f4c926cb1d0c:

  blk-cgroup: Pre-allocate tree node on blkg_conf_prep (2020-10-26 07:57:47 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-5.10-2020-10-29

for you to fetch changes up to 3c3751f2daf6675f6b5bee83b792354c272f5bd2:

  nvmet: fix a NULL pointer dereference when tracing the flush command (2020-10-27 10:02:50 +0100)

----------------------------------------------------------------
nvme updates for 5.10:

 - improve zone revalidation (Keith Busch)
 - gracefully handle zero length messages in nvme-rdma (zhenwei pi)
 - nvme-fc error handling fixes (James Smart)
 - nvmet tracing NULL pointer dereference fix (Chaitanya Kulkarni)

----------------------------------------------------------------
Chaitanya Kulkarni (1):
      nvmet: fix a NULL pointer dereference when tracing the flush command

James Smart (4):
      nvme-fc: track error_recovery while connecting
      nvme-fc: remove err_work work item
      nvme-fc: eliminate terminate_io use by nvme_fc_error_recovery
      nvme-fc: remove nvme_fc_terminate_io()

Keith Busch (1):
      nvme: ignore zone validate errors on subsequent scans

zhenwei pi (1):
      nvme-rdma: handle unexpected nvme completion data length

 drivers/nvme/host/core.c    |   2 +-
 drivers/nvme/host/fc.c      | 270 ++++++++++++++++++--------------------------
 drivers/nvme/host/rdma.c    |   8 ++
 drivers/nvme/target/core.c  |   4 +-
 drivers/nvme/target/trace.h |  21 ++--
 5 files changed, 127 insertions(+), 178 deletions(-)

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

             reply	other threads:[~2020-10-29 14:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 14:49 Christoph Hellwig [this message]
2020-10-29 14:49 ` [GIT PULL] nvme fixes for 5.10 Christoph Hellwig
2020-10-29 14:54 ` Jens Axboe
2020-10-29 14:54   ` Jens Axboe
2020-11-05  7:56 Christoph Hellwig
2020-11-05  7:56 ` Christoph Hellwig
2020-11-05 14:11 ` Jens Axboe
2020-11-05 14:11   ` Jens Axboe
2020-11-19  7:50 Christoph Hellwig
2020-11-19  7:50 ` Christoph Hellwig
2020-11-19 16:23 ` Jens Axboe
2020-11-19 16:23   ` 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=20201029144934.GA143642@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.