mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "yu kuai" <yukuai@fygo.io>
To: "Zizhi Wo" <wozizhi@huawei.com>, <song@kernel.org>,
	 <magiclinan@didiglobal.com>, <xiao@kernel.org>,
	 <linux-raid@vger.kernel.org>, "yu kuai" <yukuai@fygo.io>
Cc: <linux-kernel@vger.kernel.org>, <yangerkun@huawei.com>,
	 <chengzhihao1@huawei.com>
Subject: Re: [PATCH V2 0/2] md/raid10: annotate lockless access and fix hungtask
Date: Sat, 5 Sep 2026 09:24:37 +0800	[thread overview]
Message-ID: <463a91ea-4448-4a0c-9fe7-c42c1c4fad38@fygo.io> (raw)
In-Reply-To: <20260817033340.418119-1-wozizhi@huawei.com>

在 2026/8/17 11:33, Zizhi Wo 写道:

> Patch 1 annotates the lockless access to conf->array_freeze_pending with
> READ_ONCE()/WRITE_ONCE(). No functional change.
>
> Patch 2 fixes a hungtask in raid10.
>
> Changes in v2:
> - Add patch 1 to annotate the lockless reads of conf->array_freeze_pending
>    with READ_ONCE(), paried with WRITE_ONCE() on the write side.
> - Use READ_ONCE() when reading conf->array_freeze_pending in patch 2.
>
> v1:
> https://lore.kernel.org/all/20260810135521.3470422-1-wozizhi@huaweicloud.com/
>
> Zizhi Wo (2):
>    md/raid10: annotate lockless access to array_freeze_pending
>    md/raid10: fix missing wakeup in wait_barrier_nolock
>
>   drivers/md/raid10.c | 9 +++++----
>   1 file changed, 5 insertions(+), 4 deletions(-)
Applied to md-7.3
>
-- 
Thanks,
Kuai

      parent reply	other threads:[~2026-09-05  1:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  3:33 Zizhi Wo
2026-08-17  3:33 ` [PATCH V2 1/2] md/raid10: annotate lockless access to array_freeze_pending Zizhi Wo
2026-08-17  3:33 ` [PATCH V2 2/2] md/raid10: fix missing wakeup in wait_barrier_nolock Zizhi Wo
2026-08-17 10:53   ` Abd-Alrhman Masalkhi
2026-09-05  1:24 ` 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=463a91ea-4448-4a0c-9fe7-c42c1c4fad38@fygo.io \
    --to=yukuai@fygo.io \
    --cc=chengzhihao1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=magiclinan@didiglobal.com \
    --cc=song@kernel.org \
    --cc=wozizhi@huawei.com \
    --cc=xiao@kernel.org \
    --cc=yangerkun@huawei.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

all inboxes | Powered by JetHome®