Linux-Raid Archives mirror
 help / color / mirror / Atom feed
From: linan666@huaweicloud.com
To: song@kernel.org, mariusz.tkaczyk@linux.intel.com, shli@fb.com,
	neilb@suse.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 v6 0/9] bugfix of MD_CLOSING and clean up md_ioctl()
Date: Tue,  6 Feb 2024 16:55:02 +0800	[thread overview]
Message-ID: <20240206085511.2841555-1-linan666@huaweicloud.com> (raw)

From: Li Nan <linan122@huawei.com>

Changes in v6:
 - in patch 2, return directly.
 - in patch 4, return directly in case GET_DISK_INFO and GET_ARRAY_INFO.
 - in patch 7, rewrite commit message.
 - add patch 8, clean up openers check.

Changes in v5:
 - add patches 1-4 to clean up md_ioct(), pathc 4 can help us clean up
   local variable 'clear_md_closing'.
 - in patches 5 and 7, clean up local variable 'clear_md_closing'.

By the way, md_ioctl() is not readable now, I wanna to re-write it later
to make it only have one 'switch' like other drivers.

Li Nan (9):
  md: merge the check of capabilities into md_ioctl_valid()
  md: changed the switch of RAID_VERSION to if
  md: clean up invalid BUG_ON in md_ioctl
  md: return directly before setting did_set_md_closing
  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: clean up openers check in do_md_stop() and md_set_readonly()
  md: check mddev->pers before calling md_set_readonly()

 drivers/md/md.c | 190 ++++++++++++++++++++++++------------------------
 1 file changed, 94 insertions(+), 96 deletions(-)

-- 
2.39.2


             reply	other threads:[~2024-02-06  8:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06  8:55 linan666 [this message]
2024-02-06  8:55 ` [PATCH v6 1/9] md: merge the check of capabilities into md_ioctl_valid() linan666
2024-02-06  8:55 ` [PATCH v6 2/9] md: changed the switch of RAID_VERSION to if linan666
2024-02-06  8:55 ` [PATCH v6 3/9] md: clean up invalid BUG_ON in md_ioctl linan666
2024-02-06  8:55 ` [PATCH v6 4/9] md: return directly before setting did_set_md_closing linan666
2024-02-06  8:55 ` [PATCH v6 5/9] md: Don't clear MD_CLOSING when the raid is about to stop linan666
2024-02-06  8:55 ` [PATCH v6 6/9] md: factor out a helper to sync mddev linan666
2024-02-06  8:55 ` [PATCH v6 7/9] md: sync blockdev before stopping raid or setting readonly linan666
2024-02-06  8:55 ` [PATCH v6 8/9] md: clean up openers check in do_md_stop() and md_set_readonly() linan666
2024-02-06  8:55 ` [PATCH v6 9/9] md: check mddev->pers before calling md_set_readonly() linan666
2024-02-12 23:36 ` [PATCH v6 0/9] bugfix of MD_CLOSING and clean up md_ioctl() Song Liu
2024-02-21  9:15   ` Li Nan

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=20240206085511.2841555-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).