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.16-rc4
Date: Fri, 27 Jun 2025 08:25:32 -0600 [thread overview]
Message-ID: <63eaea99-fa38-4aef-8254-934ec0504067@kernel.dk> (raw)
Hi Linus,
Here are a set of block fixes that should go into the 6.16 kernel
release. This pull request contains:
- Fixes for ublk
- Fix C++ narrowing warnings in the uapi header
- Update/improve UBLK_F_SUPPORT_ZERO_COPY comment in uapi header
- Fix for the ublk ->queue_rqs() implementation, limiting a
batch to just the specific task AND ring
- ublk_get_data() error handling fix
- Sanity check more arguments in ublk_ctrl_add_dev()
- selftest addition
- NVMe pull request via Christoph
- reset delayed remove_work after reconnect
- fix atomic write size validation
- Fix for a warning introduced in bdev_count_inflight_rw() in this merge
window
Please pull!
The following changes since commit 8c8472855884355caf3d8e0c50adf825f83454b2:
ublk: santizize the arguments from userspace when adding a device (2025-06-19 07:53:24 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/block-6.16-20250626
for you to fetch changes up to c007062188d8e402c294117db53a24b2bed2b83f:
block: fix false warning in bdev_count_inflight_rw() (2025-06-26 07:34:11 -0600)
----------------------------------------------------------------
block-6.16-20250626
----------------------------------------------------------------
Caleb Sander Mateos (2):
ublk: fix narrowing warnings in UAPI header
ublk: update UBLK_F_SUPPORT_ZERO_COPY comment in UAPI header
Christoph Hellwig (2):
nvme: refactor the atomic write unit detection
nvme: fix atomic write size validation
Jens Axboe (1):
Merge tag 'nvme-6.16-2025-06-26' of git://git.infradead.org/nvme into block-6.16
Keith Busch (1):
nvme: reset delayed remove_work after reconnect
Ming Lei (3):
ublk: build batch from IOs in same io_ring_ctx and io task
selftests: ublk: don't take same backing file for more than one ublk devices
ublk: setup ublk_io correctly in case of ublk_get_data() failure
Ronnie Sahlberg (1):
ublk: sanity check add_dev input for underflow
Yu Kuai (1):
block: fix false warning in bdev_count_inflight_rw()
block/genhd.c | 26 ++++----
drivers/block/ublk_drv.c | 49 +++++++++++----
drivers/nvme/host/core.c | 87 +++++++++++++-------------
drivers/nvme/host/multipath.c | 2 +-
drivers/nvme/host/nvme.h | 3 +-
include/uapi/linux/ublk_cmd.h | 32 ++++++++--
tools/testing/selftests/ublk/test_stress_03.sh | 5 +-
7 files changed, 125 insertions(+), 79 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-06-27 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 14:25 Jens Axboe [this message]
2025-06-27 16:29 ` [GIT PULL] Block fixes for 6.16-rc4 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=63eaea99-fa38-4aef-8254-934ec0504067@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