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.18
Date: Tue, 29 Mar 2022 09:31:45 +0200 [thread overview]
Message-ID: <YkK14fRnn3GVpGxQ@infradead.org> (raw)
The following changes since commit b2479de38d8fc7ef13d5c78ff5ded6e5a1a4eac0:
n64cart: convert bi_disk to bi_bdev->bd_disk fix build (2022-03-21 06:34:45 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.18-2022-03-29
for you to fetch changes up to a4a6f3c8f61c3cfbda4998ad94596059ad7e4332:
nvme-multipath: fix hang when disk goes live over reconnect (2022-03-29 09:29:06 +0200)
----------------------------------------------------------------
for Linux 5.18
- fix multipath hang when disk goes live over reconnect (Anton Eidelman)
- fix RCU hole that allowed for endless looping in multipath round robin
(Chris Leech)
- remove redundant assignment after left shift (Colin Ian King)
- add quirks for Samsung X5 SSDs (Monish Kumar R)
- fix the read-only state for zoned namespaces with unsupposed features
(Pankaj Raghav)
- use a private workqueue instead of the system workqueue in nvmet
(Sagi Grimberg)
- allow duplicate NSIDs for private namespaces (Sungup Moon)
- expose use_threaded_interrupts read-only in sysfs (Xin Hao)
----------------------------------------------------------------
Anton Eidelman (1):
nvme-multipath: fix hang when disk goes live over reconnect
Chris Leech (1):
nvme: fix RCU hole that allowed for endless looping in multipath round robin
Colin Ian King (1):
nvmet: remove redundant assignment after left shift
Monish Kumar R (1):
nvme-pci: add quirks for Samsung X5 SSDs
Pankaj Raghav (1):
nvme: fix the read-only state for zoned namespaces with unsupposed features
Sagi Grimberg (1):
nvmet: use a private workqueue instead of the system workqueue
Sungup Moon (1):
nvme: allow duplicate NSIDs for private namespaces
Xin Hao (1):
nvme-pci: expose use_threaded_interrupts read-only in sysfs
drivers/nvme/host/core.c | 38 ++++++++++++++++++++++++++------------
drivers/nvme/host/multipath.c | 32 +++++++++++++++++++++++++++-----
drivers/nvme/host/nvme.h | 23 +++++++++++++++++++++++
drivers/nvme/host/pci.c | 7 +++++--
drivers/nvme/target/admin-cmd.c | 2 +-
drivers/nvme/target/configfs.c | 2 +-
drivers/nvme/target/core.c | 26 +++++++++++++++++++-------
drivers/nvme/target/fc.c | 8 ++++----
drivers/nvme/target/fcloop.c | 16 ++++++++--------
drivers/nvme/target/io-cmd-file.c | 6 +++---
drivers/nvme/target/loop.c | 4 ++--
drivers/nvme/target/nvmet.h | 1 +
drivers/nvme/target/passthru.c | 2 +-
drivers/nvme/target/rdma.c | 12 ++++++------
drivers/nvme/target/tcp.c | 10 +++++-----
include/linux/nvme.h | 1 +
16 files changed, 133 insertions(+), 57 deletions(-)
next reply other threads:[~2022-03-29 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 7:31 Christoph Hellwig [this message]
2022-03-29 12:24 ` [GIT PULL] nvme fixes for Linux 5.18 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2022-04-15 5:01 Christoph Hellwig
2022-04-15 12:34 ` 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=YkK14fRnn3GVpGxQ@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