linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.com>
To: Guoqing Jiang <gqjiang@suse.com>gqjiang@suse.com
Cc: linux-raid@vger.kernel.org, rgoldwyn@suse.com
Subject: Re: [PATCH 1/2] md-cluster: update comments for MD_CLUSTER_SEND_LOCKED_ALREADY
Date: Wed, 09 Dec 2015 08:17:34 +1100	[thread overview]
Message-ID: <87bna0skr5.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <1449253972-26997-1-git-send-email-gqjiang@suse.com>

[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]

On Sat, Dec 05 2015, Guoqing Jiang wrote:

> 1. fix unbalanced parentheses.
> 2. add more description about that MD_CLUSTER_SEND_LOCKED_ALREADY
>    will be cleared after set it in add_new_disk.
>
> Signed-off-by: Guoqing Jiang <gqjiang@suse.com>

Applied, thanks.

NeilBrown

> ---
>  drivers/md/md-cluster.c | 23 ++++++++++++++++++-----
>  1 file changed, 18 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/md/md-cluster.c b/drivers/md/md-cluster.c
> index ad3ec7d..0ded8e9 100644
> --- a/drivers/md/md-cluster.c
> +++ b/drivers/md/md-cluster.c
> @@ -53,11 +53,12 @@ struct resync_info {
>   * accomodate lock and hold. See next comment.
>   */
>  #define		MD_CLUSTER_SEND_LOCK			4
> -/* If cluster operations must lock the communication channel,
> - * so as to perform extra operations (and no other operation
> - * is allowed on the MD, such as adding a disk. Token needs
> - * to be locked and held until the operation completes with
> - * a md_update_sb(), which would eventually release the lock.
> +/* If cluster operations (such as adding a disk) must lock the
> + * communication channel, so as to perform extra operations
> + * (update metadata) and no other operation is allowed on the
> + * MD. Token needs to be locked and held until the operation
> + * completes witha md_update_sb(), which would eventually release
> + * the lock.
>   */
>  #define		MD_CLUSTER_SEND_LOCKED_ALREADY		5
>  
> @@ -1021,6 +1022,18 @@ static int add_new_disk(struct mddev *mddev, struct md_rdev *rdev)
>  		unlock_comm(cinfo);
>  	else {
>  		dlm_lock_sync(cinfo->no_new_dev_lockres, DLM_LOCK_CR);
> +		/* Since MD_CHANGE_DEVS will be set in add_bound_rdev which
> +		 * will run soon after add_new_disk, the below path will be
> +		 * invoked:
> +		 *   md_wakeup_thread(mddev->thread)
> +		 *	-> conf->thread (raid1d)
> +		 *	-> md_check_recovery -> md_update_sb
> +		 *	-> metadata_update_start/finish
> +		 * MD_CLUSTER_SEND_LOCKED_ALREADY will be cleared eventually.
> +		 *
> +		 * For other failure cases, metadata_update_cancel and
> +		 * add_new_disk_cancel also clear below bit as well.
> +		 * */
>  		set_bit(MD_CLUSTER_SEND_LOCKED_ALREADY, &cinfo->state);
>  		wake_up(&cinfo->wait);
>  	}
> -- 
> 2.1.4

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

      parent reply	other threads:[~2015-12-08 21:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 18:32 [PATCH 1/2] md-cluster: update comments for MD_CLUSTER_SEND_LOCKED_ALREADY Guoqing Jiang
2015-12-04 18:32 ` [PATCH 2/2] md: update comment for md_allow_write Guoqing Jiang
2015-12-08 21:17   ` NeilBrown
2015-12-08 21:17 ` NeilBrown [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=87bna0skr5.fsf@notabene.neil.brown.name \
    --to=neilb@suse.com \
    --cc=gqjiang@suse.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rgoldwyn@suse.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).