linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guoqing Jiang <gqjiang@suse.com>
To: jes.sorensen@gmail.com
Cc: linux-raid@vger.kernel.org, Guoqing Jiang <gqjiang@suse.com>
Subject: [PATCH V2 0/3] Make dlm lock more reliable for cluster-md
Date: Wed,  3 Jan 2018 16:19:08 +0800	[thread overview]
Message-ID: <20180103081911.7380-1-gqjiang@suse.com> (raw)

For V2, there are some change in the first patch.

1. confirm a device in slave node doen't need to get lock.
2. remove the explicitly name of dlm library.
3. delete a global variable which was used for store lockid.

However, I am not able to simplify the checks before call lock_cluster
in the first patch ...

Thanks,
Guoqing
---------------------------------------------------------------------
Currently, only a few functions which change superblock are protected
by dlm lock, but to avoid consistent issue we need to protect those
funcs which read superblock.

And call dlm locking interface inside super1.c is really clumsy since
each func which accesses superblock should be protected by dlm lock,
so we call lock_cluster/unlock_cluster in mdadm.c.

The first patch provides dlm locking support for CREATE, MANAGE, GROW
and INCREMENTAL mode, then the second patch provides the support for
ASSEMBLE mode. The last patch cleanup the failure path in Assemble().

Guoqing Jiang (3):
  mdadm: improve the dlm locking mechanism for clustered raid
  Assemble: provide protection when clustered raid do assemble
  Assemble: cleanup the failure path

 Assemble.c | 82 ++++++++++++++++++++++++++++++++++++--------------------------
 mdadm.c    | 20 +++++++++++++++
 mdadm.h    | 12 +++++----
 super1.c   | 42 --------------------------------
 util.c     | 73 +++++++++++++++++++++++++++++++++++++++++++++----------
 5 files changed, 135 insertions(+), 94 deletions(-)

-- 
2.13.6


             reply	other threads:[~2018-01-03  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03  8:19 Guoqing Jiang [this message]
2018-01-03  8:19 ` [PATCH V2 1/3] mdadm: improve the dlm locking mechanism for clustered raid Guoqing Jiang
2018-01-21 21:08   ` Jes Sorensen
2018-01-22  3:18     ` Guoqing Jiang
2018-01-03  8:19 ` [PATCH V2 2/3] Assemble: provide protection when clustered raid do assemble Guoqing Jiang
2018-01-03  8:19 ` [PATCH V2 3/3] Assemble: cleanup the failure path Guoqing Jiang

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=20180103081911.7380-1-gqjiang@suse.com \
    --to=gqjiang@suse.com \
    --cc=jes.sorensen@gmail.com \
    --cc=linux-raid@vger.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 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).