From: linan666@huaweicloud.com
To: song@kernel.org, neilb@suse.com, shli@fb.com,
mariusz.tkaczyk@linux.intel.com
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
linan666@huaweicloud.com, yukuai3@huawei.com,
yi.zhang@huawei.com, houtao1@huawei.com, yangerkun@huawei.com
Subject: [PATCH v4 0/4] md: Don't clear MD_CLOSING when the raid is about to stop
Date: Fri, 26 Jan 2024 17:22:50 +0800 [thread overview]
Message-ID: <20240126092254.1314908-1-linan666@huaweicloud.com> (raw)
From: Li Nan <linan122@huawei.com>
Changes in v4:
- insert 'break;' to avoid fall-through in patch 3.
Changes in v3:
- rename vaires 'did_set_md_closing' in patch 1.
- rename function mddev_set_closing_and_sync_blockdev() in patch 2.
- reorganize conditions in patch 3.
- add a new patch to clean up md_set_readonly().
Changes in v2:
- don't clear MD_CLOSING in md_clean().
- set MD_CLOSING and sync blockdev in array_state_store().
Li Nan (4):
md: Don't clear MD_CLOSING when the raid is about to stop
md: factor out a helper to sync mddev
md: sync blockdev before stopping raid or setting readonly
md: check mddev->pers before calling md_set_readonly()
drivers/md/md.c | 98 ++++++++++++++++++++++++++++++++++---------------
1 file changed, 69 insertions(+), 29 deletions(-)
--
2.39.2
next reply other threads:[~2024-01-26 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 9:22 linan666 [this message]
2024-01-26 9:22 ` [PATCH v4 1/4] md: Don't clear MD_CLOSING when the raid is about to stop linan666
2024-01-27 8:38 ` Yu Kuai
2024-01-26 9:22 ` [PATCH v4 2/4] md: factor out a helper to sync mddev linan666
2024-01-26 9:22 ` [PATCH v4 3/4] md: sync blockdev before stopping raid or setting readonly linan666
2024-01-26 9:22 ` [PATCH v4 4/4] md: check mddev->pers before calling md_set_readonly() linan666
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=20240126092254.1314908-1-linan666@huaweicloud.com \
--to=linan666@huaweicloud.com \
--cc=houtao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=neilb@suse.com \
--cc=shli@fb.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).