From: Yu Kuai <yukuai1@huaweicloud.com>
To: Song Liu <song@kernel.org>, Yu Kuai <yukuai1@huaweicloud.com>
Cc: mariusz.tkaczyk@linux.intel.com, xni@redhat.com,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, yangerkun@huawei.com,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH v2 1/2] md: factor out a new helper to put mddev
Date: Wed, 27 Sep 2023 08:54:54 +0800 [thread overview]
Message-ID: <94ef3ef4-0580-416b-f672-250a91b39e10@huaweicloud.com> (raw)
In-Reply-To: <CAPhsuW4dXrwt7VTifcdbdwH6Uz3b4m4Z54fBfD3LDjXy89PTkQ@mail.gmail.com>
Hi,
在 2023/09/27 8:15, Song Liu 写道:
> On Mon, Sep 25, 2023 at 8:04 PM Yu Kuai <yukuai1@huaweicloud.com> wrote:
>>
>> From: Yu Kuai <yukuai3@huawei.com>
>>
>> There are no functional changes, the new helper will still hold
>> 'all_mddevs_lock' after putting mddev, and it will be used to simplify
>> md_seq_ops.
>>
>> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
>> ---
>> drivers/md/md.c | 18 +++++++++++++++---
>> 1 file changed, 15 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/md/md.c b/drivers/md/md.c
>> index 10cb4dfbf4ae..a5ef6f7da8ec 100644
>> --- a/drivers/md/md.c
>> +++ b/drivers/md/md.c
>> @@ -616,10 +616,15 @@ static inline struct mddev *mddev_get(struct mddev *mddev)
>>
>> static void mddev_delayed_delete(struct work_struct *ws);
>>
>> -void mddev_put(struct mddev *mddev)
>> +static void __mddev_put(struct mddev *mddev, bool locked)
>> {
>> - if (!atomic_dec_and_lock(&mddev->active, &all_mddevs_lock))
>> + if (locked) {
>> + spin_lock(&all_mddevs_lock);
>> + if (!atomic_dec_and_test(&mddev->active))
>> + return;
>> + } else if (!atomic_dec_and_lock(&mddev->active, &all_mddevs_lock))
>> return;
>> +
>
> This condition is indeed very confusing. No matter whether we call the
> flag "locked" or "do_lock", it is not really accurate.
>
> How about we factor out a helper with the following logic:
>
> if (!mddev->raid_disks && list_empty(&mddev->disks) &&
> mddev->ctime == 0 && !mddev->hold_active) {
> /* Array is not configured at all, and not held active,
> * so destroy it */
> set_bit(MD_DELETED, &mddev->flags);
>
> /*
> * Call queue_work inside the spinlock so that
> * flush_workqueue() after mddev_find will succeed in waiting
> * for the work to be done.
> */
> queue_work(md_misc_wq, &mddev->del_work);
> }
>
> and then use it at the two callers?
>
> Does this make sense?
Yes, that sounds great. I'll do this in v3.
Thanks,
Kuai
>
> Thanks,
> Song
> .
>
next prev parent reply other threads:[~2023-09-27 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 2:58 [PATCH v2 0/2] md: simplify md_seq_ops Yu Kuai
2023-09-26 2:58 ` [PATCH v2 1/2] md: factor out a new helper to put mddev Yu Kuai
2023-09-26 12:45 ` Mariusz Tkaczyk
2023-09-26 12:54 ` Yu Kuai
2023-09-26 13:19 ` Mariusz Tkaczyk
2023-09-27 0:15 ` Song Liu
2023-09-27 0:54 ` Yu Kuai [this message]
2023-09-26 2:58 ` [PATCH v2 2/2] md: simplify md_seq_ops Yu Kuai
2023-09-26 14:09 ` Mariusz Tkaczyk
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=94ef3ef4-0580-416b-f672-250a91b39e10@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=song@kernel.org \
--cc=xni@redhat.com \
--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).