linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yu Kuai <yukuai1@huaweicloud.com>
To: Benjamin Marzinski <bmarzins@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>,
	Mikulas Patocka <mpatocka@redhat.com>, Song Liu <song@kernel.org>
Cc: Heinz Mauelshagen <heinzm@redhat.com>, Xiao Ni <xni@redhat.com>,
	dm-devel@lists.linux.dev, linux-raid@vger.kernel.org,
	Yu Kuai <yukuai1@huaweicloud.com>,
	"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH v2] dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume
Date: Thu, 13 Jun 2024 11:50:51 +0800	[thread overview]
Message-ID: <b4bae533-d4cb-37ab-b24c-42375c256448@huaweicloud.com> (raw)
In-Reply-To: <20240612181222.877577-1-bmarzins@redhat.com>

Hi,

在 2024/06/13 2:12, Benjamin Marzinski 写道:
> rm-raid devices will occasionally trigger the following warning when
dm-raid

> being resumed after a table load because DM_RECOVERY_RUNNING is set:
> 
> WARNING: CPU: 7 PID: 5660 at drivers/md/dm-raid.c:4105 raid_resume+0xee/0x100 [dm_raid]
> 
> The failing check is:
> WARN_ON_ONCE(test_bit(MD_RECOVERY_RUNNING, &mddev->recovery));
> 
> This check is designed to make sure that the sync thread isn't
> registered, but md_check_recovery can set MD_RECOVERY_RUNNING without
> the sync_thread ever getting registered. Instead of checking if
> MD_RECOVERY_RUNNING is set, check if sync_thread is non-NULL.
> 
> Fixes: 16c4770c75b1 ("dm-raid: really frozen sync_thread during suspend")
> Suggested-by: Yu Kuai <yukuai1@huaweicloud.com>
Please use the address yukuai3@huawei.com

> Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
> ---
> Changes in v2:
>   - Move mddev_lock_nointr() earlier to protect dereference and use
>     rcu_dereference_protected() to access sync_thread
> 
>   drivers/md/dm-raid.c | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/md/dm-raid.c b/drivers/md/dm-raid.c
> index abe88d1e6735..b149ac46a990 100644
> --- a/drivers/md/dm-raid.c
> +++ b/drivers/md/dm-raid.c
> @@ -4101,10 +4101,11 @@ static void raid_resume(struct dm_target *ti)
>   		if (mddev->delta_disks < 0)
>   			rs_set_capacity(rs);
>   
> +		mddev_lock_nointr(mddev);
>   		WARN_ON_ONCE(!test_bit(MD_RECOVERY_FROZEN, &mddev->recovery));
> -		WARN_ON_ONCE(test_bit(MD_RECOVERY_RUNNING, &mddev->recovery));
> +		WARN_ON_ONCE(rcu_dereference_protected(mddev->sync_thread,
> +						       lockdep_is_held(&mddev->reconfig_mutex)));
>   		clear_bit(RT_FLAG_RS_FROZEN, &rs->runtime_flags);
> -		mddev_lock_nointr(mddev);

Other than the typo, LGTM

Suggested-and-reviewed-by: Yu Kuai <yukuai3@huawei.com>
>   		mddev->ro = 0;
>   		mddev->in_sync = 0;
>   		md_unfrozen_sync_thread(mddev);
> 


      reply	other threads:[~2024-06-13  3:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 18:12 [PATCH v2] dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume Benjamin Marzinski
2024-06-13  3:50 ` Yu Kuai [this message]

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=b4bae533-d4cb-37ab-b24c-42375c256448@huaweicloud.com \
    --to=yukuai1@huaweicloud.com \
    --cc=bmarzins@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=heinzm@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@kernel.org \
    --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).