From: "yu kuai" <yukuai@fygo.io>
To: "Abd-Alrhman Masalkhi" <abd.masalkhi@gmail.com>,
<song@kernel.org>, <magiclinan@didiglobal.com>,
<xiao@kernel.org>, <axboe@kernel.dk>, <vverma@digitalocean.com>,
<john.g.garry@oracle.com>, <martin.petersen@oracle.com>,
<linux-kernel@vger.kernel.org>, "yu kuai" <yukuai@fygo.io>
Cc: <linux-raid@vger.kernel.org>
Subject: Re: [PATCH v4 0/7] md/raid10: fixes, atomic write handling, and error-path cleanup
Date: Fri, 31 Jul 2026 08:35:42 +0800 [thread overview]
Message-ID: <41ecd70b-14af-4747-b24f-7cf9b9aa3e75@fygo.io> (raw)
In-Reply-To: <20260710101521.1714-1-abd.masalkhi@gmail.com>
Hi,
在 2026/7/10 18:15, Abd-Alrhman Masalkhi 写道:
> Hi,
>
> This v4 of series contains a mix of bug fixes and cleanups for RAID10,
> along with a related atomic write fix for RAID1.
>
> Changes in v4:
> - Improve the commit message of patch 2.
> - Add Reviewed-by tag from John Garry to patch 2.
> - Link to v3: https://lore.kernel.org/linux-raid/20260708101341.473750-1-abd.masalkhi@gmail.com/
>
> Changes in v3:
> - Set chunk_sectors to BARRIER_UNIT_SECTOR_SIZE instead of setting
> atomic_write_hw_unit_max.
> - Avoid enabling write-behind when the atomic write exceeds the
> write-behind limit.
> - Link to v2: https://lore.kernel.org/linux-raid/20260628142420.1051027-1-abd.masalkhi@gmail.com/
>
> Changes in v2:
> - Expand the commit message to explain why the
> allow_barrier()/wait_barrier() pair is no longer needed.
> - Drop the early atomic write split check from raid1_write_request().
> - Advertise the atomic write size limit via queue limits.
> - Disable write-behind instead of failing atomic writes when the
> BIO_MAX_VECS limit is encountered.
> - Drop the early atomic write split check from raid10_write_request()
> and rely on queue limits instead.
> - Fix a compilation error (bi -> bio).
> - Link to v1: https://lore.kernel.org/linux-raid/20260623072456.333437-1-abd.masalkhi@gmail.com/
>
> Thanks,
> Abd-alrhman,
>
> Abd-Alrhman Masalkhi (7):
> md/raid10: fix r10bio leak in raid10_write_request() error paths
> md/raid1: restrict atomic write limits and handle runtime constraints
> md/raid10: consistently fail atomic writes that require splitting
> md/raid10: remove unnecessary barrier around bio_submit_split_bioset()
> md/raid10: replace wait loop with wait_event_idle()
> md/raid10: simplify write request error handling
> md/raid10: simplify read request error handling
Applied patch 2,3,4 to md-7.3
Both patch 1 and patch 5 is not needed after your nowait patch.
>
> drivers/md/raid1.c | 25 ++++------
> drivers/md/raid10.c | 118 +++++++++++++++++++++-----------------------
> 2 files changed, 65 insertions(+), 78 deletions(-)
>
--
Thanks,
Kuai
prev parent reply other threads:[~2026-07-31 0:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 10:15 [PATCH v4 0/7] md/raid10: fixes, atomic write handling, and error-path cleanup Abd-Alrhman Masalkhi
2026-07-10 10:15 ` [PATCH v4 1/7] md/raid10: fix r10bio leak in raid10_write_request() error paths Abd-Alrhman Masalkhi
2026-07-10 10:31 ` sashiko-bot
2026-07-15 7:35 ` yu kuai
2026-07-10 10:15 ` [PATCH v4 2/7] md/raid1: restrict atomic write limits and handle runtime constraints Abd-Alrhman Masalkhi
2026-07-15 9:09 ` yu kuai
2026-07-10 10:15 ` [PATCH v4 3/7] md/raid10: consistently fail atomic writes that require splitting Abd-Alrhman Masalkhi
2026-07-10 10:28 ` sashiko-bot
2026-07-15 9:10 ` yu kuai
2026-07-15 9:25 ` John Garry
2026-07-15 10:05 ` Abd-Alrhman Masalkhi
2026-07-15 10:49 ` John Garry
2026-07-15 11:16 ` Abd-Alrhman Masalkhi
2026-07-10 10:15 ` [PATCH v4 4/7] md/raid10: remove unnecessary barrier around bio_submit_split_bioset() Abd-Alrhman Masalkhi
2026-07-16 9:24 ` yu kuai
2026-07-10 10:15 ` [PATCH v4 5/7] md/raid10: replace wait loop with wait_event_idle() Abd-Alrhman Masalkhi
2026-07-16 9:25 ` yu kuai
2026-07-10 10:15 ` [PATCH v4 6/7] md/raid10: simplify write request error handling Abd-Alrhman Masalkhi
2026-07-10 10:15 ` [PATCH v4 7/7] md/raid10: simplify read " Abd-Alrhman Masalkhi
2026-07-16 9:52 ` yu kuai
2026-07-23 8:43 ` Abd-Alrhman Masalkhi
2026-07-31 0:35 ` yu kuai [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=41ecd70b-14af-4747-b24f-7cf9b9aa3e75@fygo.io \
--to=yukuai@fygo.io \
--cc=abd.masalkhi@gmail.com \
--cc=axboe@kernel.dk \
--cc=john.g.garry@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=magiclinan@didiglobal.com \
--cc=martin.petersen@oracle.com \
--cc=song@kernel.org \
--cc=vverma@digitalocean.com \
--cc=xiao@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