public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaohua Li <shli@kernel.org>
To: NeilBrown <neilb@suse.com>
Cc: Shaohua Li <shli@fb.com>, Guoqing Jiang <gqjiang@suse.com>,
	linux-raid@vger.kernel.org
Subject: Re: [PATCH] md: ensure md devices are freed before module is unloaded.
Date: Mon, 6 Feb 2017 12:03:09 -0800	[thread overview]
Message-ID: <20170206200309.ryu7dg6hjczsibao@kernel.org> (raw)
In-Reply-To: <87r33cvy58.fsf@notabene.neil.brown.name>

On Mon, Feb 06, 2017 at 01:41:39PM +1100, Neil Brown wrote:
> 
> 
> Commit: cbd199837750 ("md: Fix unfortunate interaction with evms")
> change mddev_put() so that it would not destroy an md device while
> ->ctime was non-zero.
> 
> Unfortunately, we didn't make sure to clear ->ctime when unloading
> the module, so it is possible for an md device to remain after
> module unload.  An attempt to open such a device will trigger
> an invalid memory reference in:
>   get_gendisk -> kobj_lookup -> exact_lock -> get_disk
> 
> when tring to access disk->fops, which was in the module that has
> been removed.
> 
> So ensure we clear ->ctime in md_exit(), and explain how that is useful,
> as it isn't immediately obvious when looking at the code.
> 
> Fixes: cbd199837750 ("md: Fix unfortunate interaction with evms")
> Tested-by: Guoqing Jiang <gqjiang@suse.com>
> Signed-off-by: NeilBrown <neilb@suse.com>
Applied, thanks!

> ---
>  drivers/md/md.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index 01175dac0db6..8926fb781cdc 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -8980,7 +8980,14 @@ static __exit void md_exit(void)
>  
>  	for_each_mddev(mddev, tmp) {
>  		export_array(mddev);
> +		mddev->ctime = 0;
>  		mddev->hold_active = 0;
> +		/* for_each_mddev() will call mddev_put() at the
> +		 * end of each iteration.  As the mddev is now
> +		 * fully clear, this will schedule the mddev for destruction
> +		 * by a workqueue, and the destroy_workqueue() below
> +		 * will wait for that to complete.
> +		 */
>  	}
>  	destroy_workqueue(md_misc_wq);
>  	destroy_workqueue(md_wq);
> -- 
> 2.11.0
> 



      reply	other threads:[~2017-02-06 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06  2:41 [PATCH] md: ensure md devices are freed before module is unloaded NeilBrown
2017-02-06 20:03 ` Shaohua Li [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=20170206200309.ryu7dg6hjczsibao@kernel.org \
    --to=shli@kernel.org \
    --cc=gqjiang@suse.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=shli@fb.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