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] second row of nvme updates for Linux 5.20
Date: Wed, 27 Jul 2022 12:01:11 -0400 [thread overview]
Message-ID: <YuFhR9OoPvM9VsdT@infradead.org> (raw)
Against the for-5.20/drivers-post tree.
The following changes since commit 2dc9e74e37124f1b43ea60157e5990fd490c6e8f:
remove the sx8 block driver (2022-07-25 17:25:18 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.20-2022-07-27
for you to fetch changes up to 26203a5e04d5cb1d1715f71c48cf6eec0dd9b88f:
nvme: update MAINTAINERS for the new auth code (2022-07-26 16:04:27 -0400)
----------------------------------------------------------------
nvme updates for Linux 5.20
- use command_id instead of req->tag in trace_nvme_complete_rq()
(Bean Huo)
- various fixes for the new authentication code (Lukas Bulwahn,
Dan Carpenter, Colin Ian King, Chaitanya Kulkarni, Hannes Reinecke)
- small cleanups (Liu Song, Christoph Hellwig)
- restore compat_ioctl support (Nick Bowler)
- make a nvmet-tcp workqueue lockdep-safe (Sagi Grimberg)
- enable generic interface (/dev/ngXnY) for unknown command sets
(Joel Granados, Christoph Hellwig)
- don't always build constants.o (Christoph Hellwig)
- print the command name of aborted commands (Christoph Hellwig)
----------------------------------------------------------------
Bean Huo (1):
nvme: use command_id instead of req->tag in trace_nvme_complete_rq()
Chaitanya Kulkarni (2):
nvmet-auth: fix return value check in auth send
nvmet-auth: fix return value check in auth receive
Christoph Hellwig (15):
nvme: don't always build constants.o
nvme-pci: print the command name of aborted commands
nvme-pci: split nvme_alloc_admin_tags
nvme-pci: split nvme_dev_add
nvme-rdma: split nvme_rdma_alloc_tagset
nvme-tcp: split nvme_tcp_alloc_tagset
nvme-apple: stop casting function pointer signatures
nvmet: don't check for NULL pointer before kfree in nvmet_host_release
nvmet: fix a format specifier in nvmet_auth_ctrl_exponential
nvme: catch -ENODEV from nvme_revalidate_zones again
nvme: rename nvme_validate_or_alloc_ns to nvme_scan_ns
nvme: generalize the nvme_multi_css check in nvme_scan_ns
nvme: refactor namespace probing
nvme: factor out a nvme_ns_is_readonly helper
nvme: update MAINTAINERS for the new auth code
Colin Ian King (1):
nvmet-auth: fix a couple of spelling mistakes
Dan Carpenter (2):
nvme-auth: fix off by one checks
nvme-auth: uninitialized variable in nvme_auth_transform_key()
Hannes Reinecke (1):
nvme-auth: fixup kernel test robot warnings
Joel Granados (1):
nvme: enable generic interface (/dev/ngXnY) for unknown command sets
Liu Song (1):
nvme-pci: remove useless assignment in nvme_pci_setup_prps
Lukas Bulwahn (1):
nvmet-auth: select the intended CRYPTO_DH_RFC7919_GROUPS
Nick Bowler (1):
nvme: define compat_ioctl again to unbreak 32-bit userspace.
Sagi Grimberg (1):
nvmet-tcp: fix lockdep complaint on nvmet_tcp_wq flush during queue teardown
MAINTAINERS | 3 +-
drivers/nvme/common/auth.c | 57 ++++---
drivers/nvme/host/Makefile | 3 +-
drivers/nvme/host/apple.c | 21 ++-
drivers/nvme/host/constants.c | 3 +-
drivers/nvme/host/core.c | 302 +++++++++++++++++++--------------
drivers/nvme/host/multipath.c | 1 +
drivers/nvme/host/pci.c | 139 +++++++--------
drivers/nvme/host/rdma.c | 92 +++++-----
drivers/nvme/host/tcp.c | 82 ++++-----
drivers/nvme/host/trace.h | 2 +-
drivers/nvme/target/Kconfig | 2 +-
drivers/nvme/target/auth.c | 4 +-
drivers/nvme/target/configfs.c | 4 +-
drivers/nvme/target/fabrics-cmd-auth.c | 7 +-
drivers/nvme/target/tcp.c | 3 +-
16 files changed, 398 insertions(+), 327 deletions(-)
next reply other threads:[~2022-07-27 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 16:01 Christoph Hellwig [this message]
2022-07-27 16:07 ` [GIT PULL] second row of nvme updates for Linux 5.20 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=YuFhR9OoPvM9VsdT@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.