From: Jens Axboe <axboe@kernel.dk>
To: Yu Kuai <yukuai@kernel.org>
Cc: linux-raid@vger.kernel.org, linux-block@vger.kernel.org,
Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>,
Chen Cheng <chencheng@fnnas.com>
Subject: Re: [GIT PULL] md-7.2-20260623
Date: Wed, 24 Jun 2026 06:33:41 -0600 [thread overview]
Message-ID: <354f8038-e402-42d3-a706-6c1fac284e0d@kernel.dk> (raw)
In-Reply-To: <20260623090327.1097428-1-yukuai@kernel.org>
On 6/23/26 3:03 AM, Yu Kuai wrote:
> 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)
Pulled, thanks.
--
Jens Axboe
prev parent reply other threads:[~2026-06-24 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 9:03 [GIT PULL] md-7.2-20260623 Yu Kuai
2026-06-24 12:33 ` Jens Axboe [this message]
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=354f8038-e402-42d3-a706-6c1fac284e0d@kernel.dk \
--to=axboe@kernel.dk \
--cc=abd.masalkhi@gmail.com \
--cc=chencheng@fnnas.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=yukuai@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