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.13-rc2
Date: Sat, 7 Dec 2024 08:14:39 -0700 [thread overview]
Message-ID: <84108c76-7be5-481a-be44-4aede8f6fab2@kernel.dk> (raw)
Hi Linus,
A few fixes for block that should go into the 6.13-rc2 release. This
pull request contains:
- NVMe pull request via Keith
- Target fix using incorrect zero buffer (Nilay)
- Device specifc deallocate quirk fixes (Christoph, Keith)
- Fabrics fix for handling max command target bugs (Maurizio)
- Cocci fix usage for kzalloc (Yu-Chen)
- DMA size fix for host memory buffer feature (Christoph)
- Fabrics queue cleanup fixes (Chunguang)
- CPU hotplug ordering fixes
- Add missing MODULE_DESCRIPTION for rnull
- bcache error value fix
- virtio-blk queue freeze fix
Please pull!
The following changes since commit cdd30ebb1b9f36159d66f088b61aee264e649d7a:
module: Convert symbol namespace to string literal (2024-12-02 11:34:44 -0800)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/block-6.13-20241207
for you to fetch changes up to 22465bbac53c821319089016f268a2437de9b00a:
blk-mq: move cpuhp callback registering out of q->sysfs_lock (2024-12-06 09:48:46 -0700)
----------------------------------------------------------------
block-6.13-20241207
----------------------------------------------------------------
Christoph Hellwig (2):
nvme: don't apply NVME_QUIRK_DEALLOCATE_ZEROES when DSM is not supported
nvme-pci: don't use dma_alloc_noncontiguous with 0 merge boundary
Chunguang.xu (4):
nvme-tcp: fix the memleak while create new ctrl failed
nvme-rdma: unquiesce admin_q before destroy it
nvme-tcp: no need to quiesce admin_q in nvme_tcp_teardown_io_queues()
nvme-tcp: simplify nvme_tcp_teardown_io_queues()
FUJITA Tomonori (1):
block: rnull: add missing MODULE_DESCRIPTION
Jens Axboe (1):
Merge tag 'nvme-6.13-2024-12-05' of git://git.infradead.org/nvme into block-6.13
Keith Busch (1):
nvme-pci: remove two deallocate zeroes quirks
Liequan Che (1):
bcache: revert replacing IS_ERR_OR_NULL with IS_ERR again
Maurizio Lombardi (1):
nvme-fabrics: handle zero MAXCMD without closing the connection
Ming Lei (3):
virtio-blk: don't keep queue frozen during system suspend
blk-mq: register cpuhp callback after hctx is added to xarray table
blk-mq: move cpuhp callback registering out of q->sysfs_lock
Nilay Shroff (1):
nvmet: use kzalloc instead of ZERO_PAGE in nvme_execute_identify_ns_nvm()
Yu-Chun Lin (1):
nvmet: replace kmalloc + memset with kzalloc for data allocation
block/blk-mq.c | 108 ++++++++++++++++++++++++++++++++++------
drivers/block/rnull.rs | 1 +
drivers/block/virtio_blk.c | 7 ++-
drivers/md/bcache/super.c | 2 +-
drivers/nvme/host/core.c | 8 +--
drivers/nvme/host/pci.c | 7 ++-
drivers/nvme/host/rdma.c | 8 +--
drivers/nvme/host/tcp.c | 17 ++-----
drivers/nvme/target/admin-cmd.c | 9 +++-
drivers/nvme/target/pr.c | 3 +-
10 files changed, 123 insertions(+), 47 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-12-07 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 15:14 Jens Axboe [this message]
2024-12-07 18:53 ` [GIT PULL] Block fixes for 6.13-rc2 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=84108c76-7be5-481a-be44-4aede8f6fab2@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 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.