From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Cc: io-uring@vger.kernel.org,
Caleb Sander Mateos <csander@purestorage.com>,
huang-jl <huang-jl@deepseek.com>,
Nitesh Shetty <nj.shetty@samsung.com>,
Ming Lei <ming.lei@redhat.com>
Subject: [PATCH 0/3] block: fix bi_vcnt misuse for cloned bio
Date: Thu, 18 Dec 2025 17:31:41 +0800 [thread overview]
Message-ID: <20251218093146.1218279-1-ming.lei@redhat.com> (raw)
Hello Guys,
The 1st patch removes .bi_vcnt from bio_may_need_split() because the
incoming bio may be cloned.
The 2nd patch doesn't initialize cloned bio's bi_vcnt in
bio_iov_bvec_set().
The 3rd patch removes iov iter nr_segs re-calculation for io_import_kbuf().
Ming Lei (3):
block: fix bio_may_need_split() by using bvec iterator way
block: don't initialize bi_vcnt for cloned bio in bio_iov_bvec_set()
io_uring: don't re-calculate iov_iter nr_segs in io_import_kbuf()
block/bio.c | 2 +-
block/blk.h | 13 ++++++++++---
io_uring/rsrc.c | 10 ----------
3 files changed, 11 insertions(+), 14 deletions(-)
--
2.47.0
next reply other threads:[~2025-12-18 9:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 9:31 Ming Lei [this message]
2025-12-18 9:31 ` [PATCH 1/3] block: fix bio_may_need_split() by using bvec iterator way Ming Lei
2025-12-18 9:37 ` Christoph Hellwig
2025-12-18 9:45 ` Ming Lei
2025-12-18 15:16 ` Nitesh Shetty
2025-12-18 16:08 ` Ming Lei
2025-12-20 8:16 ` Nitesh Shetty
2025-12-20 8:19 ` Nitesh Shetty
2025-12-18 9:31 ` [PATCH 2/3] block: don't initialize bi_vcnt for cloned bio in bio_iov_bvec_set() Ming Lei
2025-12-18 9:38 ` Christoph Hellwig
2025-12-18 9:48 ` Ming Lei
2025-12-18 9:31 ` [PATCH 3/3] io_uring: don't re-calculate iov_iter nr_segs in io_import_kbuf() Ming Lei
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=20251218093146.1218279-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=huang-jl@deepseek.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=nj.shetty@samsung.com \
/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