From: Yu Kuai <yukuai1@huaweicloud.com>
To: Xiao Ni <xni@redhat.com>, Yu Kuai <yukuai1@huaweicloud.com>
Cc: linux-raid@vger.kernel.org, song@kernel.org, ncroxon@redhat.com,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH 2/3] md: replace MD_DELETED with MD_CLOSING
Date: Fri, 9 May 2025 18:26:31 +0800 [thread overview]
Message-ID: <04bc114d-08f8-b703-de7e-2f828f41321b@huaweicloud.com> (raw)
In-Reply-To: <CALTww28OBZZYdD_fJdFjmsjo51cn7CvVrKe=yserF+xvMd5f0A@mail.gmail.com>
Hi,
在 2025/05/09 18:20, Xiao Ni 写道:
> On Fri, May 9, 2025 at 6:08 PM Yu Kuai <yukuai1@huaweicloud.com> wrote:
>>
>> Hi,
>>
>> 在 2025/05/09 17:33, Xiao Ni 写道:
>>> The two places clear MD_CLOSING rather than setting MD_CLOSING.
>>> MD_CLOSING is set when we really want to stop the array (STOP_ARRAY
>>> cmd and clear>array_state_store). So the two places clear MD_CLOSING
>>> for other situations which look good to me.
>>
>> No, MD_CLOSING can be set first in the two cases, do something and then
>> be cleared, that's why I said temporarily.
>
> So you mean mddev_get should pass in this case (between setting
> MD_CLOSING and clearing MD_CLOSING)? It doesn't allow get mddev now
> without this patch. This should be right.
I don't understand what you mean "It doesn't allow get mddev now without
this patch", for example, the ioctl STOP_ARRAY_RO will set MD_CLOSING
temporarily, but never set MD_DELETED, mddev_get() can always pass.
Thanks,
Kuai
>
> Regardes
> Xiao
>
>>
>> Thanks,
>> Kuai
>>
>
>
> .
>
next prev parent reply other threads:[~2025-05-09 10:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 2:14 [PATCH 0/3] md: call del_gendisk in sync way Xiao Ni
2025-05-07 2:14 ` [PATCH 1/3] md: Don't clear MD_CLOSING until mddev is freed Xiao Ni
2025-05-07 2:14 ` [PATCH 2/3] md: replace MD_DELETED with MD_CLOSING Xiao Ni
2025-05-07 6:20 ` Yu Kuai
2025-05-09 9:33 ` Xiao Ni
2025-05-09 10:08 ` Yu Kuai
2025-05-09 10:20 ` Xiao Ni
2025-05-09 10:26 ` Yu Kuai [this message]
2025-05-09 11:20 ` Xiao Ni
2025-05-12 1:39 ` Yu Kuai
2025-05-07 2:14 ` [PATCH 3/3] md: call del_gendisk in sync way Xiao Ni
2025-05-07 6:28 ` Yu Kuai
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=04bc114d-08f8-b703-de7e-2f828f41321b@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=linux-raid@vger.kernel.org \
--cc=ncroxon@redhat.com \
--cc=song@kernel.org \
--cc=xni@redhat.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).