From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme updates for Linux 6.2
Date: Tue, 29 Nov 2022 09:56:28 +0100 [thread overview]
Message-ID: <Y4XJPNP74KmdI8+7@infradead.org> (raw)
This is just the first round, there is quite a bit more in the queue.
The following changes since commit 5626196a5ae0937368b35c3625c428a2125b0f44:
Merge branch 'md-next' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into for-6.2/block (2022-11-14 12:57:50 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.2-2022-11-29
for you to fetch changes up to 68c5444c317208f5a114f671140373f47f0a2cf6:
nvmet: expose firmware revision to configfs (2022-11-21 08:35:58 +0100)
----------------------------------------------------------------
nvme updates for Linux 6.2
- support some passthrough commands without CAP_SYS_ADMIN
(Kanchan Joshi)
- refactor PCIe probing and reset (Christoph Hellwig)
- various fabrics authentication fixes and improvements (Sagi Grimberg)
- avoid fallback to sequential scan due to transient issues
(Uday Shankar)
- implement support for the DEAC bit in Write Zeroes (Christoph Hellwig)
- allow overriding the IEEE OUI and firmware revision in configfs for
nvmet (Aleksandr Miloserdov)
- force reconnect when number of queue changes in nvmet (Daniel Wagner)
- minor fixes and improvements (Uros Bizjak, Joel Granados,
Sagi Grimberg, Christoph Hellwig, Christophe JAILLET)
----------------------------------------------------------------
Aleksandr Miloserdov (2):
nvmet: expose IEEE OUI to configfs
nvmet: expose firmware revision to configfs
Christoph Hellwig (16):
nvmet: only allocate a single slab for bvecs
nvme: implement the DEAC bit for the Write Zeroes command
nvme: don't call nvme_init_ctrl_finish from nvme_passthru_end
nvme: move OPAL setup from PCIe to core
nvme: simplify transport specific device attribute handling
nvme-pci: put the admin queue in nvme_dev_remove_admin
nvme-pci: move more teardown work to nvme_remove
nvme-pci: factor the iod mempool creation into a helper
nvme-pci: factor out a nvme_pci_alloc_dev helper
nvme-pci: set constant paramters in nvme_pci_alloc_ctrl
nvme-pci: call nvme_pci_configure_admin_queue from nvme_pci_enable
nvme-pci: simplify nvme_dbbuf_dma_alloc
nvme-pci: move the HMPRE check into nvme_setup_host_mem
nvme-pci: split the initial probe from the rest path
nvme-pci: don't unbind the driver on reset failure
nvme: rename the queue quiescing helpers
Christophe JAILLET (1):
nvme-fc: improve memory usage in nvme_fc_rcv_ls_req()
Daniel Wagner (1):
nvmet: force reconnect when number of queue changes
Joel Granados (1):
nvme: return err on nvme_init_non_mdts_limits fail
Kanchan Joshi (2):
nvme: fine-granular CAP_SYS_ADMIN for nvme io commands
nvme: identify-namespace without CAP_SYS_ADMIN
Sagi Grimberg (20):
nvme-auth: rename __nvme_auth_[reset|free] to nvme_auth[reset|free]_dhchap
nvme-auth: rename authentication work elements
nvme-auth: remove symbol export from nvme_auth_reset
nvme-auth: don't re-authenticate if the controller is not LIVE
nvme-auth: remove redundant buffer deallocations
nvme-auth: don't ignore key generation failures when initializing ctrl keys
nvme-auth: don't override ctrl keys before validation
nvme-auth: remove redundant if statement
nvme-auth: don't keep long lived 4k dhchap buffer
nvme-auth: guarantee dhchap buffers under memory pressure
nvme-auth: clear sensitive info right after authentication completes
nvme-auth: remove redundant deallocations
nvme-auth: no need to reset chap contexts on re-authentication
nvme-auth: check chap ctrl_key once constructed
nvme-auth: convert dhchap_auth_list to an array
nvme-auth: remove redundant auth_work flush
nvme-auth: have dhchap_auth_work wait for queues auth to complete
nvme-tcp: stop auth work after tearing down queues in error recovery
nvme-rdma: stop auth work after tearing down queues in error recovery
nvmet: fix a memory leak in nvmet_auth_set_key
Uday Shankar (1):
nvme: avoid fallback to sequential scan due to transient issues
Uros Bizjak (1):
nvmet: use try_cmpxchg in nvmet_update_sq_head
drivers/nvme/host/apple.c | 14 +-
drivers/nvme/host/auth.c | 258 ++++++++++++-----------
drivers/nvme/host/core.c | 125 ++++++++---
drivers/nvme/host/fc.c | 35 ++--
drivers/nvme/host/ioctl.c | 116 ++++++++---
drivers/nvme/host/nvme.h | 35 ++--
drivers/nvme/host/pci.c | 423 ++++++++++++++++++--------------------
drivers/nvme/host/rdma.c | 30 +--
drivers/nvme/host/tcp.c | 32 +--
drivers/nvme/target/admin-cmd.c | 9 +-
drivers/nvme/target/auth.c | 2 +
drivers/nvme/target/configfs.c | 121 ++++++++++-
drivers/nvme/target/core.c | 44 ++--
drivers/nvme/target/io-cmd-file.c | 16 +-
drivers/nvme/target/loop.c | 8 +-
drivers/nvme/target/nvmet.h | 6 +-
include/linux/nvme.h | 2 +
17 files changed, 766 insertions(+), 510 deletions(-)
next reply other threads:[~2022-11-29 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 8:56 Christoph Hellwig [this message]
2022-11-29 13:56 ` [GIT PULL] nvme updates for Linux 6.2 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2022-12-07 18:28 Christoph Hellwig
2022-12-07 19:40 ` 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=Y4XJPNP74KmdI8+7@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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