linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yu Kuai <yukuai1@huaweicloud.com>
To: Yu Kuai <yukuai1@huaweicloud.com>, Xiao Ni <xni@redhat.com>,
	linux-raid@vger.kernel.org
Cc: ncroxon@redhat.com, song@kernel.org, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH 1/3] md: call del_gendisk in control path
Date: Fri, 6 Jun 2025 16:48:51 +0800	[thread overview]
Message-ID: <cd3e67e6-05c2-56f8-9bcc-c95d0f05df92@huaweicloud.com> (raw)
In-Reply-To: <30a77424-e5f4-ee83-52a2-cab7e3cbc1ed@huaweicloud.com>

Hi,

在 2025/06/06 16:46, Yu Kuai 写道:
> +    if (!ret && test_bit(MD_DELETED, &mddev->flags)) {
> +        ret = -EBUSY;

And I think ENODEV is better here.

Thanks,
Kuai


  reply	other threads:[~2025-06-06  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04  9:07 [PATCH V4 0/3] md: call del_gendisk in sync way Xiao Ni
2025-06-04  9:07 ` [PATCH 1/3] md: call del_gendisk in control path Xiao Ni
2025-06-06  8:46   ` Yu Kuai
2025-06-06  8:48     ` Yu Kuai [this message]
2025-06-09  9:15       ` Xiao Ni
2025-06-04  9:07 ` [PATCH 2/3] md: Don't clear MD_CLOSING until mddev is freed Xiao Ni
2025-06-04  9:07 ` [PATCH 3/3] md: remove/add redundancy group only in level change Xiao Ni
  -- strict thread matches above, loose matches on Subject: below --
2025-06-11  7:31 [PATCH V6 0/3] md: call del_gendisk in sync way Xiao Ni
2025-06-11  7:31 ` [PATCH 1/3] md: call del_gendisk in control path Xiao Ni
2025-06-10  7:20 [PATCH V5 0/3] md: call del_gendisk in sync way Xiao Ni
2025-06-10  7:20 ` [PATCH 1/3] md: call del_gendisk in control path Xiao Ni
2025-06-11  6:09   ` Yu Kuai
2025-06-03  5:20 [PATCH V3 0/2] md: call del_gendisk in sync way Xiao Ni
2025-06-03  5:20 ` [PATCH 1/3] md: call del_gendisk in control path Xiao Ni

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=cd3e67e6-05c2-56f8-9bcc-c95d0f05df92@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).