From: Mark Fasheh <mfasheh@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 2/6] Add DLM recovery callbacks
Date: Sun, 3 Nov 2013 14:16:44 -0800 [thread overview]
Message-ID: <20131103221644.GH29346@wotan.suse.de> (raw)
In-Reply-To: <20131018144520.GA4579@shrek.lan>
This also looks good in that I don't see anything wrong with the way the
actual code functions. The extra description you put about the callbacks
helps in understanding this too. Question - can you explain why oc_this_node
is an atomic? That is to say I'd like to understand that race that you're
protecting against :)
--Mark
On Fri, Oct 18, 2013 at 09:45:25AM -0500, Goldwyn Rodrigues wrote:
> These are the callbacks called by the fs/dlm code in case the membership
> changes. If there is a failure while/during calling any of these, the
> DLM creates a new membership and relays to the rest of the nodes.
>
> recover_prep() is called when DLM understands a node is down.
> recover_slot() is called once all nodes have acknowledged recover_prep
> and recovery can begin.
> recover_done() is called once the recovery is complete. It returns the
> new membership.
>
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
> ---
> fs/ocfs2/stack_user.c | 38 ++++++++++++++++++++++++++++++++++++++
> 1 file changed, 38 insertions(+)
>
> diff --git a/fs/ocfs2/stack_user.c b/fs/ocfs2/stack_user.c
> index 286edf1..4111855 100644
> --- a/fs/ocfs2/stack_user.c
> +++ b/fs/ocfs2/stack_user.c
> @@ -110,6 +110,8 @@
> struct ocfs2_live_connection {
> struct list_head oc_list;
> struct ocfs2_cluster_connection *oc_conn;
> + atomic_t oc_this_node;
> + int oc_our_slot;
> };
>
> struct ocfs2_control_private {
> @@ -799,6 +801,42 @@ static int fs_protocol_compare(struct ocfs2_protocol_version *existing,
> return 0;
> }
>
> +static void user_recover_prep(void *arg)
> +{
> +}
> +
> +static void user_recover_slot(void *arg, struct dlm_slot *slot)
> +{
> + struct ocfs2_cluster_connection *conn = arg;
> + printk(KERN_INFO "ocfs2: Node %d/%d down. Initiating recovery.\n",
> + slot->nodeid, slot->slot);
> + conn->cc_recovery_handler(slot->nodeid, conn->cc_recovery_data);
> +
> +}
> +
> +static void user_recover_done(void *arg, struct dlm_slot *slots,
> + int num_slots, int our_slot,
> + uint32_t generation)
> +{
> + struct ocfs2_cluster_connection *conn = arg;
> + struct ocfs2_live_connection *lc = conn->cc_private;
> + int i;
> +
> + for (i = 0; i < num_slots; i++)
> + if (slots[i].slot == our_slot) {
> + atomic_set(&lc->oc_this_node, slots[i].nodeid);
> + break;
> + }
> +
> + lc->oc_our_slot = our_slot;
> +}
> +
> +const struct dlm_lockspace_ops ocfs2_ls_ops = {
> + .recover_prep = user_recover_prep,
> + .recover_slot = user_recover_slot,
> + .recover_done = user_recover_done,
> +};
> +
> static int user_cluster_connect(struct ocfs2_cluster_connection *conn)
> {
> dlm_lockspace_t *fsdlm;
> --
> 1.8.1.4
>
>
> --
> Goldwyn
--
Mark Fasheh
next prev parent reply other threads:[~2013-11-03 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 14:45 [Ocfs2-devel] [PATCH 2/6] Add DLM recovery callbacks Goldwyn Rodrigues
2013-11-03 22:16 ` Mark Fasheh [this message]
2013-11-04 3:45 ` Goldwyn Rodrigues
2013-11-04 22:09 ` Mark Fasheh
2013-11-05 20:34 ` Goldwyn Rodrigues
-- strict thread matches above, loose matches on Subject: below --
2013-11-12 14:06 Goldwyn Rodrigues
2013-11-25 23:00 ` Mark Fasheh
2013-12-09 19:41 Goldwyn Rodrigues
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=20131103221644.GH29346@wotan.suse.de \
--to=mfasheh@suse.de \
--cc=ocfs2-devel@oss.oracle.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