From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: [GIT PULL] nvme fixes for Linux 6.9
Date: Thu, 2 May 2024 14:00:27 +0100 [thread overview]
Message-ID: <ZjOOa7KiIGnOjlDM@kbusch-mbp.dhcp.thefacebook.com> (raw)
Jens:
I am on travel right now, and I've lost communication with my remote
server with my signing and push keys; therefore this does not have a
tag, much less a signed one. Since nvme is a bit behind on our pull
requests, I would like to get this out before the next rc. You can ping
me on back channel if you want to verify the legitimacy of the pull.
The following changes since commit 013ee5a6234d4c574dedd60c4887a4bcc9ecc749:
Merge tag 'md-6.9-20240408' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into block-6.9 (2024-04-08 21:49:27 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git 50abcc179e0c9ca667feb223b26ea406d5c4c556
for you to fetch changes up to 50abcc179e0c9ca667feb223b26ea406d5c4c556:
nvme-tcp: strict pdu pacing to avoid send stalls on TLS (2024-05-01 02:58:43 -0700)
----------------------------------------------------------------
Hannes Reinecke (1):
nvme-tcp: strict pdu pacing to avoid send stalls on TLS
Maurizio Lombardi (2):
nvmet-auth: return the error code to the nvmet_auth_host_hash() callers
nvmet-auth: replace pr_debug() with pr_err() to report an error.
Nilay Shroff (2):
nvme: find numa distance only if controller has valid numa id
nvme: cancel pending I/O if nvme controller is in terminal state
Sagi Grimberg (2):
nvmet-tcp: fix possible memory leak when tearing down a controller
nvmet: fix nvme status code when namespace is disabled
Yi Zhang (1):
nvme: fix warn output about shared namespaces without CONFIG_NVME_MULTIPATH
drivers/nvme/host/core.c | 23 +----------------------
drivers/nvme/host/multipath.c | 3 ++-
drivers/nvme/host/nvme.h | 21 +++++++++++++++++++++
drivers/nvme/host/pci.c | 8 +++++++-
drivers/nvme/host/tcp.c | 10 ++++++++--
drivers/nvme/target/auth.c | 8 ++++----
drivers/nvme/target/configfs.c | 13 +++++++++++++
drivers/nvme/target/core.c | 5 ++++-
drivers/nvme/target/nvmet.h | 1 +
drivers/nvme/target/tcp.c | 11 ++++-------
10 files changed, 65 insertions(+), 38 deletions(-)
next reply other threads:[~2024-05-02 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 13:00 Keith Busch [this message]
2024-05-02 13:46 ` [GIT PULL] nvme fixes for Linux 6.9 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2024-05-09 17:48 Keith Busch
2024-05-09 17:50 ` Jens Axboe
2024-04-04 16:59 Keith Busch
2024-04-04 19: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=ZjOOa7KiIGnOjlDM@kbusch-mbp.dhcp.thefacebook.com \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).