From: Yu Kuai <yukuai1@huaweicloud.com>
To: Song Liu <song@kernel.org>, Yu Kuai <yukuai1@huaweicloud.com>
Cc: Li Nan <linan122@huawei.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, houtao1@huawei.com, yangerkun@huawei.com,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] md: use interruptible apis in idle/frozen_sync_thread
Date: Thu, 28 Sep 2023 14:31:41 +0800 [thread overview]
Message-ID: <382b6c81-598b-52be-c09a-2f5b293b8d69@huaweicloud.com> (raw)
In-Reply-To: <CAPhsuW4FjWohGYzWGocF+zxMcLRk7N3J8T45=QXzAmdqFFuNTA@mail.gmail.com>
Hi,
在 2023/09/09 4:29, Song Liu 写道:
> On Wed, Sep 6, 2023 at 11:31 PM Yu Kuai <yukuai1@huaweicloud.com> wrote:
>>
>> 在 2023/09/06 16:44, Li Nan 写道:
>>> Before refactoring idle and frozen from action_store, interruptible apis
>>> is used so that hungtask warning won't be triggered if it takes too long
>>> to finish indle/frozen sync_thread. So change to use interruptible apis.
>>>
>> LGTM
>>
>> Reviewed-by: Yu Kuai <yukuai3@huawei.com>
>>
>>> Signed-off-by: Li Nan <linan122@huawei.com>
>
> I think we will need a fix tag and send this via md-fixes branch (to 6.6)?
>
I agree, Nan, please resend this patch.
Thanks,
Kuai
> Thanks,
> Song
>
>
>
>>> ---
>>> drivers/md/md.c | 13 +++++++++----
>>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/drivers/md/md.c b/drivers/md/md.c
>>> index 46badd13a687..52689adfa37f 100644
>>> --- a/drivers/md/md.c
>>> +++ b/drivers/md/md.c
>>> @@ -4834,11 +4834,14 @@ static void idle_sync_thread(struct mddev *mddev)
>>> {
>>> int sync_seq = atomic_read(&mddev->sync_seq);
>>>
>>> - mutex_lock(&mddev->sync_mutex);
>>> + if (mutex_lock_interruptible(&mddev->sync_mutex))
>>> + return;
>>> +
>>> clear_bit(MD_RECOVERY_FROZEN, &mddev->recovery);
>>> stop_sync_thread(mddev);
>>>
>>> - wait_event(resync_wait, sync_seq != atomic_read(&mddev->sync_seq) ||
>>> + wait_event_interruptible(resync_wait,
>>> + sync_seq != atomic_read(&mddev->sync_seq) ||
>>> !test_bit(MD_RECOVERY_RUNNING, &mddev->recovery));
>>>
>>> mutex_unlock(&mddev->sync_mutex);
>>> @@ -4846,11 +4849,13 @@ static void idle_sync_thread(struct mddev *mddev)
>>>
>>> static void frozen_sync_thread(struct mddev *mddev)
>>> {
>>> - mutex_lock(&mddev->sync_mutex);
>>> + if (mutex_lock_interruptible(&mddev->sync_mutex))
>>> + return;
>>> +
>>> set_bit(MD_RECOVERY_FROZEN, &mddev->recovery);
>>> stop_sync_thread(mddev);
>>>
>>> - wait_event(resync_wait, mddev->sync_thread == NULL &&
>>> + wait_event_interruptible(resync_wait, mddev->sync_thread == NULL &&
>>> !test_bit(MD_RECOVERY_RUNNING, &mddev->recovery));
>>>
>>> mutex_unlock(&mddev->sync_mutex);
>>>
>>
> .
>
prev parent reply other threads:[~2023-09-28 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 8:44 [PATCH] md: use interruptible apis in idle/frozen_sync_thread Li Nan
[not found] ` <e2befbc6-dfc4-f469-78f0-b648d0ad205d@huaweicloud.com>
2023-09-08 20:29 ` Song Liu
2023-09-28 6:31 ` 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=382b6c81-598b-52be-c09a-2f5b293b8d69@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=houtao1@huawei.com \
--cc=linan122@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@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;
as well as URLs for NNTP newsgroup(s).