From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 6.9-rc7
Date: Fri, 3 May 2024 08:30:18 -0600 [thread overview]
Message-ID: <442223dc-d734-4c8e-abf8-1e89e92eb1ec@kernel.dk> (raw)
Hi Linus,
Nothing major in here - an nvme pull request with mostly auth/tcp fixes,
and a single fix for ublk not setting segment count and size limits.
Please pull!
The following changes since commit 01bc4fda9ea0a6b52f12326486f07a4910666cf6:
blk-iocost: do not WARN if iocg was already offlined (2024-04-19 08:06:24 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/block-6.9-20240503
for you to fetch changes up to fb15ffd06115047689d05897510b423f9d144461:
Merge commit '50abcc179e0c9ca667feb223b26ea406d5c4c556' of git://git.infradead.org/nvme into block-6.9 (2024-05-02 07:22:51 -0600)
----------------------------------------------------------------
block-6.9-20240503
----------------------------------------------------------------
Hannes Reinecke (1):
nvme-tcp: strict pdu pacing to avoid send stalls on TLS
Jens Axboe (1):
Merge commit '50abcc179e0c9ca667feb223b26ea406d5c4c556' of git://git.infradead.org/nvme into block-6.9
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
Uday Shankar (1):
ublk: remove segment count and size limits
Yi Zhang (1):
nvme: fix warn output about shared namespaces without CONFIG_NVME_MULTIPATH
drivers/block/ublk_drv.c | 3 ++-
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 ++++-------
11 files changed, 67 insertions(+), 39 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-05-03 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 14:30 Jens Axboe [this message]
2024-05-03 16:41 ` [GIT PULL] Block fixes for 6.9-rc7 pr-tracker-bot
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=442223dc-d734-4c8e-abf8-1e89e92eb1ec@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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