linux-block.vger.kernel.org archive mirror
 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 Linux 5.13
Date: Thu, 13 May 2021 19:03:40 +0200	[thread overview]
Message-ID: <YJ1b7OeZpoR3j13K@infradead.org> (raw)

The following changes since commit efed9a3337e341bd0989161b97453b52567bc59d:

  kyber: fix out of bounds access when preempted (2021-05-11 08:12:14 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-5.13-2021-05-13

for you to fetch changes up to e181811bd04d874fe48bbfa1165a82068b58144d:

  nvmet: use new ana_log_size instead the old one (2021-05-13 16:33:32 +0200)

----------------------------------------------------------------
nvme fix for Linux 5.13

 - correct the check for using the inline bio in nvmet
   (Chaitanya Kulkarni)
 - demote unsupported command warnings (Chaitanya Kulkarni)
 - fix corruption due to double initializing ANA state (me, Hou Pu)
 - reset ns->file when open fails (Daniel Wagner)
 - fix a NULL deref when SEND is completed with error in nvmet-rdma
   (Michal Kalderon)

----------------------------------------------------------------
Chaitanya Kulkarni (5):
      nvmet: fix inline bio check for bdev-ns
      nvmet: fix inline bio check for passthru
      nvmet: demote discovery cmd parse err msg to debug
      nvmet: use helper to remove the duplicate code
      nvmet: demote fabrics cmd parse err msg to debug

Christoph Hellwig (1):
      nvme-multipath: fix double initialization of ANA state

Daniel Wagner (1):
      nvmet: seset ns->file when open fails

Hou Pu (1):
      nvmet: use new ana_log_size instead the old one

Michal Kalderon (1):
      nvmet-rdma: Fix NULL deref when SEND is completed with error

 drivers/nvme/host/core.c          |  3 ++-
 drivers/nvme/host/multipath.c     | 55 +++++++++++++++++++++------------------
 drivers/nvme/host/nvme.h          |  8 ++++--
 drivers/nvme/target/admin-cmd.c   |  7 ++---
 drivers/nvme/target/discovery.c   |  2 +-
 drivers/nvme/target/fabrics-cmd.c |  6 ++---
 drivers/nvme/target/io-cmd-bdev.c |  2 +-
 drivers/nvme/target/io-cmd-file.c |  8 +++---
 drivers/nvme/target/nvmet.h       |  6 +++++
 drivers/nvme/target/passthru.c    |  2 +-
 drivers/nvme/target/rdma.c        |  4 +--
 11 files changed, 58 insertions(+), 45 deletions(-)

             reply	other threads:[~2021-05-13 17:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13 17:03 Christoph Hellwig [this message]
2021-05-13 17:07 ` [GIT PULL] nvme fixes for Linux 5.13 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2021-06-03  7:05 Christoph Hellwig
2021-06-03 13:42 ` Jens Axboe
2021-05-27 11:58 Christoph Hellwig
2021-05-27 13:38 ` Jens Axboe
2021-05-20  8:00 Christoph Hellwig
2021-05-20 13:55 ` Jens Axboe
2021-05-05 14:30 Christoph Hellwig
2021-05-05 14:37 ` 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=YJ1b7OeZpoR3j13K@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).