From: Xiao Ni <xni@redhat.com>
To: Yu Kuai <yukuai1@huaweicloud.com>,
mpatocka@redhat.com, heinzm@redhat.com,
blazej.kucman@linux.intel.com, agk@redhat.com,
snitzer@kernel.org, dm-devel@lists.linux.dev, song@kernel.org,
yukuai3@huawei.com, neilb@suse.de, shli@fb.com, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
yi.zhang@huawei.com, yangerkun@huawei.com
Subject: Re: [PATCH v5 04/14] md: don't register sync_thread for reshape directly
Date: Wed, 28 Feb 2024 20:07:34 +0800 [thread overview]
Message-ID: <d233fc29-e3ab-4761-9368-c203efc0466e@redhat.com> (raw)
In-Reply-To: <20240201092559.910982-5-yukuai1@huaweicloud.com>
在 2024/2/1 下午5:25, Yu Kuai 写道:
> From: Yu Kuai <yukuai3@huawei.com>
>
> Currently, if reshape is interrupted, then reassemble the array will
> register sync_thread directly from pers->run(), in this case
> 'MD_RECOVERY_RUNNING' is set directly, however, there is no guarantee
> that md_do_sync() will be executed, hence stop_sync_thread() will hang
> because 'MD_RECOVERY_RUNNING' can't be cleared.
Hi Kuai
I have a question here. Is it the reason sync_thread can't run
md_do_sync because kthread_should_stop, so it doesn't have the chance to
set MD_RECOVERY_DONE? Why creating sync thread in md_check_recovery
doesn't have this problem? Could you explain more about this?
Best Regards
Xiao
>
> Last patch make sure that md_do_sync() will set MD_RECOVERY_DONE,
> however, following hang can still be triggered by dm-raid test
> shell/lvconvert-raid-reshape.sh occasionally:
>
> [root@fedora ~]# cat /proc/1982/stack
> [<0>] stop_sync_thread+0x1ab/0x270 [md_mod]
> [<0>] md_frozen_sync_thread+0x5c/0xa0 [md_mod]
> [<0>] raid_presuspend+0x1e/0x70 [dm_raid]
> [<0>] dm_table_presuspend_targets+0x40/0xb0 [dm_mod]
> [<0>] __dm_destroy+0x2a5/0x310 [dm_mod]
> [<0>] dm_destroy+0x16/0x30 [dm_mod]
> [<0>] dev_remove+0x165/0x290 [dm_mod]
> [<0>] ctl_ioctl+0x4bb/0x7b0 [dm_mod]
> [<0>] dm_ctl_ioctl+0x11/0x20 [dm_mod]
> [<0>] vfs_ioctl+0x21/0x60
> [<0>] __x64_sys_ioctl+0xb9/0xe0
> [<0>] do_syscall_64+0xc6/0x230
> [<0>] entry_SYSCALL_64_after_hwframe+0x6c/0x74
>
> Meanwhile mddev->recovery is:
> MD_RECOVERY_RUNNING |
> MD_RECOVERY_INTR |
> MD_RECOVERY_RESHAPE |
> MD_RECOVERY_FROZEN
>
> Fix this problem by remove the code to register sync_thread directly
> from raid10 and raid5. And let md_check_recovery() to register
> sync_thread.
>
> Fixes: f67055780caa ("[PATCH] md: Checkpoint and allow restart of raid5 reshape")
> Fixes: f52f5c71f3d4 ("md: fix stopping sync thread")
> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
> ---
> drivers/md/md.c | 5 ++++-
> drivers/md/raid10.c | 16 ++--------------
> drivers/md/raid5.c | 29 ++---------------------------
> 3 files changed, 8 insertions(+), 42 deletions(-)
>
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index c65dfd156090..6c5d0a372927 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -9372,6 +9372,7 @@ static void md_start_sync(struct work_struct *ws)
> struct mddev *mddev = container_of(ws, struct mddev, sync_work);
> int spares = 0;
> bool suspend = false;
> + char *name;
>
> if (md_spares_need_change(mddev))
> suspend = true;
> @@ -9404,8 +9405,10 @@ static void md_start_sync(struct work_struct *ws)
> if (spares)
> md_bitmap_write_all(mddev->bitmap);
>
> + name = test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery) ?
> + "reshape" : "resync";
> rcu_assign_pointer(mddev->sync_thread,
> - md_register_thread(md_do_sync, mddev, "resync"));
> + md_register_thread(md_do_sync, mddev, name));
> if (!mddev->sync_thread) {
> pr_warn("%s: could not start resync thread...\n",
> mdname(mddev));
> diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
> index 7412066ea22c..a5f8419e2df1 100644
> --- a/drivers/md/raid10.c
> +++ b/drivers/md/raid10.c
> @@ -4175,11 +4175,7 @@ static int raid10_run(struct mddev *mddev)
> clear_bit(MD_RECOVERY_SYNC, &mddev->recovery);
> clear_bit(MD_RECOVERY_CHECK, &mddev->recovery);
> set_bit(MD_RECOVERY_RESHAPE, &mddev->recovery);
> - set_bit(MD_RECOVERY_RUNNING, &mddev->recovery);
> - rcu_assign_pointer(mddev->sync_thread,
> - md_register_thread(md_do_sync, mddev, "reshape"));
> - if (!mddev->sync_thread)
> - goto out_free_conf;
> + set_bit(MD_RECOVERY_NEEDED, &mddev->recovery);
> }
>
> return 0;
> @@ -4573,16 +4569,8 @@ static int raid10_start_reshape(struct mddev *mddev)
> clear_bit(MD_RECOVERY_CHECK, &mddev->recovery);
> clear_bit(MD_RECOVERY_DONE, &mddev->recovery);
> set_bit(MD_RECOVERY_RESHAPE, &mddev->recovery);
> - set_bit(MD_RECOVERY_RUNNING, &mddev->recovery);
> -
> - rcu_assign_pointer(mddev->sync_thread,
> - md_register_thread(md_do_sync, mddev, "reshape"));
> - if (!mddev->sync_thread) {
> - ret = -EAGAIN;
> - goto abort;
> - }
> + set_bit(MD_RECOVERY_NEEDED, &mddev->recovery);
> conf->reshape_checkpoint = jiffies;
> - md_wakeup_thread(mddev->sync_thread);
> md_new_event();
> return 0;
>
> diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
> index 8497880135ee..6a7a32f7fb91 100644
> --- a/drivers/md/raid5.c
> +++ b/drivers/md/raid5.c
> @@ -7936,11 +7936,7 @@ static int raid5_run(struct mddev *mddev)
> clear_bit(MD_RECOVERY_SYNC, &mddev->recovery);
> clear_bit(MD_RECOVERY_CHECK, &mddev->recovery);
> set_bit(MD_RECOVERY_RESHAPE, &mddev->recovery);
> - set_bit(MD_RECOVERY_RUNNING, &mddev->recovery);
> - rcu_assign_pointer(mddev->sync_thread,
> - md_register_thread(md_do_sync, mddev, "reshape"));
> - if (!mddev->sync_thread)
> - goto abort;
> + set_bit(MD_RECOVERY_NEEDED, &mddev->recovery);
> }
>
> /* Ok, everything is just fine now */
> @@ -8506,29 +8502,8 @@ static int raid5_start_reshape(struct mddev *mddev)
> clear_bit(MD_RECOVERY_CHECK, &mddev->recovery);
> clear_bit(MD_RECOVERY_DONE, &mddev->recovery);
> set_bit(MD_RECOVERY_RESHAPE, &mddev->recovery);
> - set_bit(MD_RECOVERY_RUNNING, &mddev->recovery);
> - rcu_assign_pointer(mddev->sync_thread,
> - md_register_thread(md_do_sync, mddev, "reshape"));
> - if (!mddev->sync_thread) {
> - mddev->recovery = 0;
> - spin_lock_irq(&conf->device_lock);
> - write_seqcount_begin(&conf->gen_lock);
> - mddev->raid_disks = conf->raid_disks = conf->previous_raid_disks;
> - mddev->new_chunk_sectors =
> - conf->chunk_sectors = conf->prev_chunk_sectors;
> - mddev->new_layout = conf->algorithm = conf->prev_algo;
> - rdev_for_each(rdev, mddev)
> - rdev->new_data_offset = rdev->data_offset;
> - smp_wmb();
> - conf->generation --;
> - conf->reshape_progress = MaxSector;
> - mddev->reshape_position = MaxSector;
> - write_seqcount_end(&conf->gen_lock);
> - spin_unlock_irq(&conf->device_lock);
> - return -EAGAIN;
> - }
> + set_bit(MD_RECOVERY_NEEDED, &mddev->recovery);
> conf->reshape_checkpoint = jiffies;
> - md_wakeup_thread(mddev->sync_thread);
> md_new_event();
> return 0;
> }
next prev parent reply other threads:[~2024-02-28 12:07 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 9:25 [PATCH v5 00/14] dm-raid/md/raid: fix v6.7 regressions Yu Kuai
2024-02-01 9:25 ` [PATCH v5 01/14] md: don't ignore suspended array in md_check_recovery() Yu Kuai
2024-02-16 6:58 ` Xiao Ni
2024-02-18 1:14 ` Yu Kuai
2024-02-18 1:33 ` Xiao Ni
2024-02-18 1:46 ` Yu Kuai
2024-02-18 2:27 ` Xiao Ni
2024-02-18 2:34 ` Yu Kuai
2024-02-18 3:15 ` Xiao Ni
2024-02-18 3:24 ` Yu Kuai
2024-02-18 5:07 ` Xiao Ni
2024-02-18 6:22 ` Yu Kuai
2024-02-18 8:07 ` Xiao Ni
2024-02-18 8:47 ` Yu Kuai
2024-02-19 7:10 ` Xiao Ni
2024-02-19 8:19 ` Yu Kuai
2024-02-01 9:25 ` [PATCH v5 02/14] md: don't ignore read-only " Yu Kuai
2024-02-01 9:25 ` [PATCH v5 03/14] md: make sure md_do_sync() will set MD_RECOVERY_DONE Yu Kuai
2024-02-18 5:56 ` Xiao Ni
2024-02-18 6:51 ` Yu Kuai
2024-02-18 8:41 ` Xiao Ni
2024-02-18 8:59 ` Yu Kuai
2024-02-01 9:25 ` [PATCH v5 04/14] md: don't register sync_thread for reshape directly Yu Kuai
2024-02-28 12:07 ` Xiao Ni [this message]
2024-02-28 12:44 ` Yu Kuai
2024-02-28 12:57 ` Xiao Ni
2024-02-01 9:25 ` [PATCH v5 05/14] md: don't suspend the array for interrupted reshape Yu Kuai
2024-02-29 2:10 ` Xiao Ni
2024-02-29 2:14 ` Yu Kuai
2024-02-01 9:25 ` [PATCH v5 06/14] md: fix missing release of 'active_io' for flush Yu Kuai
2024-02-08 7:47 ` Song Liu
2024-02-01 9:25 ` [PATCH v5 07/14] md: export helpers to stop sync_thread Yu Kuai
2024-02-15 22:27 ` Song Liu
2024-02-18 2:35 ` Yu Kuai
2024-02-01 9:25 ` [PATCH v5 08/14] md: export helper md_is_rdwr() Yu Kuai
2024-02-01 9:25 ` [PATCH v5 09/14] dm-raid: really frozen sync_thread during suspend Yu Kuai
2024-02-18 4:53 ` Xiao Ni
2024-02-18 6:34 ` Yu Kuai
2024-02-19 7:27 ` Xiao Ni
2024-02-19 7:53 ` Yu Kuai
2024-02-19 8:45 ` Xiao Ni
2024-02-01 9:25 ` [PATCH v5 10/14] md/dm-raid: don't call md_reap_sync_thread() directly Yu Kuai
2024-02-01 9:25 ` [PATCH v5 11/14] dm-raid: add a new helper prepare_suspend() in md_personality Yu Kuai
2024-02-01 9:25 ` [PATCH v5 12/14] md/raid456: fix a deadlock for dm-raid456 while io concurrent with reshape Yu Kuai
2024-02-01 9:25 ` [PATCH v5 13/14] dm-raid: fix lockdep waring in "pers->hot_add_disk" Yu Kuai
2024-02-01 9:25 ` [PATCH v5 14/14] dm-raid: remove mddev_suspend/resume() Yu Kuai
2024-02-03 3:19 ` [PATCH v5 00/14] dm-raid/md/raid: fix v6.7 regressions Benjamin Marzinski
2024-02-04 1:35 ` Yu Kuai
2024-02-04 7:00 ` Yu Kuai
2024-02-05 19:35 ` Benjamin Marzinski
2024-02-06 1:36 ` Yu Kuai
2024-02-06 3:57 ` Benjamin Marzinski
2024-02-06 7:03 ` Yu Kuai
2024-02-08 8:04 ` Song Liu
2024-02-08 23:17 ` Benjamin Marzinski
2024-02-09 22:37 ` Song Liu
2024-02-26 7:58 ` Su Yue
2024-02-12 22:30 ` Song Liu
2024-02-15 22:24 ` Song Liu
2024-02-16 5:46 ` Benjamin Marzinski
2024-02-18 1:24 ` Yu Kuai
2024-02-19 16:05 ` Benjamin Marzinski
2024-02-20 3:09 ` Yu Kuai
2024-02-22 9:00 ` Yu Kuai
2024-02-28 1:19 ` Benjamin Marzinski
2024-02-28 1:35 ` 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=d233fc29-e3ab-4761-9368-c203efc0466e@redhat.com \
--to=xni@redhat.com \
--cc=agk@redhat.com \
--cc=akpm@osdl.org \
--cc=blazej.kucman@linux.intel.com \
--cc=dm-devel@lists.linux.dev \
--cc=heinzm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=neilb@suse.de \
--cc=shli@fb.com \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.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