From: Yu Kuai <yukuai@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-raid@vger.kernel.org, linux-block@vger.kernel.org,
Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>,
Chen Cheng <chencheng@fnnas.com>
Subject: [GIT PULL] md-7.2-20260623
Date: Tue, 23 Jun 2026 17:03:27 +0800 [thread overview]
Message-ID: <20260623090327.1097428-1-yukuai@kernel.org> (raw)
Hi Jens,
Please consider pulling the following changes into your block-7.2
branch.
This pull request contains:
Bug Fixes:
- Fix raid1 writes_pending and barrier reference leaks on write failures.
(Abd-Alrhman Masalkhi)
- Fix raid10 writes_pending leak on write request failures.
(Abd-Alrhman Masalkhi)
- Fix raid10 writes_pending and barrier reference leaks on discard failures.
(Abd-Alrhman Masalkhi)
- Fix raid1 REQ_NOWAIT handling while waiting for behind writes.
(Abd-Alrhman Masalkhi)
- Fix raid1 r1_bio leak when a REQ_NOWAIT retry would block.
(Abd-Alrhman Masalkhi)
- Fix raid1 read-balance head_position data race. (Chen Cheng)
- Fix raid5 stripe batch bm_seq wraparound comparison. (Chen Cheng)
- Fix raid5 stripe batch state snapshot KCSAN noise. (Chen Cheng)
- Fix raid5 R5_Overlap races while breaking stripe batches. (Chen Cheng)
Improvements:
- Add raid5 discard IO accounting. (Yu Kuai)
- Always convert raid5 llbitmap bits for discard. (Yu Kuai)
Cleanups:
- Simplify raid1_write_request() error handling. (Abd-Alrhman Masalkhi)
Thanks,
Kuai
---
The following changes since commit d5b58fbb2fd7ac25fcd7e1c14730f998a90b0322:
block: respect iov_iter::nofault flag in bio_iov_iter_bounce_write() (2026-06-16 14:48:35 -0600)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mdraid/linux.git md-7.2
for you to fetch changes up to 55b77337bdd088c77461588e5ec094421b89911b:
md/raid5: avoid R5_Overlap races while breaking stripe batches (2026-06-23 09:44:11 +0800)
----------------------------------------------------------------
Abd-Alrhman Masalkhi (6):
md/raid1: fix writes_pending and barrier reference leaks on write failures
md/raid10: fix writes_pending leak on write request failures
md/raid10: fix writes_pending and barrier reference leaks on discard failures
md/raid1: simplify raid1_write_request() error handling
md/raid1: honor REQ_NOWAIT when waiting for behind writes
md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry
Chen Cheng (4):
md/raid1: protect head_position for read balance
md/raid5: let stripe batch bm_seq comparison wrap-safe
md/raid5: use stripe state snapshot in break_stripe_batch_list()
md/raid5: avoid R5_Overlap races while breaking stripe batches
Yu Kuai (3):
md/raid5: account discard IO
md/raid5: validate discard support at request time
md/raid5: always convert llbitmap bits for discard
drivers/md/md-bitmap.c | 9 +++-
drivers/md/md-bitmap.h | 2 +-
drivers/md/md-llbitmap.c | 13 +++--
drivers/md/md.c | 2 +-
drivers/md/raid1.c | 99 ++++++++++++++++++++---------------
drivers/md/raid10.c | 28 +++++++---
drivers/md/raid5.c | 131 +++++++++++++++++++++++++++++------------------
drivers/md/raid5.h | 1 +
8 files changed, 178 insertions(+), 107 deletions(-)
next reply other threads:[~2026-06-23 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 9:03 Yu Kuai [this message]
2026-06-24 12:33 ` [GIT PULL] md-7.2-20260623 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=20260623090327.1097428-1-yukuai@kernel.org \
--to=yukuai@kernel.org \
--cc=abd.masalkhi@gmail.com \
--cc=axboe@kernel.dk \
--cc=chencheng@fnnas.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.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