From: Yu Kuai <yukuai1@huaweicloud.com>
To: Xiao Ni <xni@redhat.com>, linux-raid@vger.kernel.org
Cc: yukuai1@huaweicloud.com, ncroxon@redhat.com, song@kernel.org,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH 1/2] md: Don't clear MD_CLOSING until mddev is freed
Date: Fri, 30 May 2025 14:48:24 +0800 [thread overview]
Message-ID: <fed9d361-7005-d82c-d03b-6b6e5f12d4d5@huaweicloud.com> (raw)
In-Reply-To: <20250515090847.2356-2-xni@redhat.com>
在 2025/05/15 17:08, Xiao Ni 写道:
> UNTIL_STOP is used to avoid mddev is freed on the last close before adding
> disks to mddev. And it should be cleared when stopping an array which is
> mentioned in commit efeb53c0e572 ("md: Allow md devices to be created by
> name."). So reset ->hold_active to 0 in md_clean.
>
> And MD_CLOSING should be kept until mddev is freed to avoid reopen.
>
> Signed-off-by: Xiao Ni <xni@redhat.com>
> ---
> drivers/md/md.c | 15 ++++-----------
> 1 file changed, 4 insertions(+), 11 deletions(-)
>
Patch 1 applied to md-6.16
BTW, please send a new version for patch 2, we might consider it for
the next merge window.
Thanks,
Kuai
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index 9daa78c5fe33..9b9950ed6ee9 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -6360,15 +6360,10 @@ static void md_clean(struct mddev *mddev)
> mddev->persistent = 0;
> mddev->level = LEVEL_NONE;
> mddev->clevel[0] = 0;
> - /*
> - * Don't clear MD_CLOSING, or mddev can be opened again.
> - * 'hold_active != 0' means mddev is still in the creation
> - * process and will be used later.
> - */
> - if (mddev->hold_active)
> - mddev->flags = 0;
> - else
> - mddev->flags &= BIT_ULL_MASK(MD_CLOSING);
> + /* if UNTIL_STOP is set, it's cleared here */
> + mddev->hold_active = 0;
> + /* Don't clear MD_CLOSING, or mddev can be opened again. */
> + mddev->flags &= BIT_ULL_MASK(MD_CLOSING);
> mddev->sb_flags = 0;
> mddev->ro = MD_RDWR;
> mddev->metadata_type[0] = 0;
> @@ -6595,8 +6590,6 @@ static int do_md_stop(struct mddev *mddev, int mode)
> export_array(mddev);
>
> md_clean(mddev);
> - if (mddev->hold_active == UNTIL_STOP)
> - mddev->hold_active = 0;
> }
> md_new_event();
> sysfs_notify_dirent_safe(mddev->sysfs_state);
>
next prev parent reply other threads:[~2025-05-30 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 9:08 [PATCH V2 0/2] md: call del_gendisk in sync way Xiao Ni
2025-05-15 9:08 ` [PATCH 1/2] md: Don't clear MD_CLOSING until mddev is freed Xiao Ni
2025-05-27 2:01 ` Yu Kuai
2025-05-30 6:48 ` Yu Kuai [this message]
2025-05-30 6:58 ` Xiao Ni
2025-05-30 7:57 ` Xiao Ni
2025-05-30 8:11 ` Yu Kuai
2025-05-15 9:08 ` [PATCH 2/2] md: call del_gendisk in control path Xiao Ni
2025-05-27 2:11 ` 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=fed9d361-7005-d82c-d03b-6b6e5f12d4d5@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).