All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhong Lidong <lidong.zhong@suse.com>
To: song@kernel.org
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: [PATCH] md: adding a new flag MD_DELETING
Date: Sat, 8 May 2021 15:41:39 +0800	[thread overview]
Message-ID: <8c7a3fc1-eaf8-b67c-d981-29932168295f@suse.com> (raw)
In-Reply-To: <20210428082903.14783-1-lidong.zhong@suse.com>

Hi Song,

Could you share your opinion about this patch please?

Thanks,
Lidong

On 4/28/21 4:29 PM, Lidong Zhong wrote:
> The mddev data structure is freed in mddev_delayed_delete(), which is
> schedualed after the array is deconfigured completely when stopping. So
> there is a race window between md_open() and do_md_stop(), which leads
> to /dev/mdX can still be opened by userspace even it's not accessible
> any more. As a result, a DeviceDisappeared event will not be able to be
> monitored by mdadm in monitor mode. This patch tries to fix it by adding
> this new flag MD_DELETING.
> 
> Signed-off-by: Lidong Zhong <lidong.zhong@suse.com>
> ---
>  drivers/md/md.c | 4 +++-
>  drivers/md/md.h | 2 ++
>  2 files changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index 21da0c48f6c2..566df2491318 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -6439,6 +6439,7 @@ static int do_md_stop(struct mddev *mddev, int mode,
>  		md_clean(mddev);
>  		if (mddev->hold_active == UNTIL_STOP)
>  			mddev->hold_active = 0;
> +		set_bit(MD_DELETING, &mddev->flags);
>  	}
>  	md_new_event(mddev);
>  	sysfs_notify_dirent_safe(mddev->sysfs_state);
> @@ -7829,7 +7830,8 @@ static int md_open(struct block_device *bdev, fmode_t mode)
>  	if ((err = mutex_lock_interruptible(&mddev->open_mutex)))
>  		goto out;
>  
> -	if (test_bit(MD_CLOSING, &mddev->flags)) {
> +	if (test_bit(MD_CLOSING, &mddev->flags) ||
> +            (test_bit(MD_DELETING, &mddev->flags) && mddev->pers == NULL)) {
>  		mutex_unlock(&mddev->open_mutex);
>  		err = -ENODEV;
>  		goto out;
> diff --git a/drivers/md/md.h b/drivers/md/md.h
> index bcbba1b5ec4a..83c7aa61699f 100644
> --- a/drivers/md/md.h
> +++ b/drivers/md/md.h
> @@ -262,6 +262,8 @@ enum mddev_flags {
>  	MD_BROKEN,              /* This is used in RAID-0/LINEAR only, to stop
>  				 * I/O in case an array member is gone/failed.
>  				 */
> +	MD_DELETING,		/* If set, we are deleting the array, do not open
> +				 * it then */
>  };
>  
>  enum mddev_sb_flags {
> 


  reply	other threads:[~2021-05-08  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  8:29 [PATCH] md: adding a new flag MD_DELETING Lidong Zhong
2021-05-08  7:41 ` Zhong Lidong [this message]
2021-05-11  6:39   ` Song Liu
2021-06-04  1:23 ` Song Liu
2021-06-04  4:55   ` Zhong Lidong

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=8c7a3fc1-eaf8-b67c-d981-29932168295f@suse.com \
    --to=lidong.zhong@suse.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.