From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH] dlm: fix NULL ls usage
Date: Mon, 16 Jul 2007 09:48:50 +0100 [thread overview]
Message-ID: <1184575730.8765.303.camel@quoit> (raw)
In-Reply-To: <20070713194906.GB16274@redhat.com>
Hi,
Now in the -nmw GFS2 git tree. Thanks,
Steve.
On Fri, 2007-07-13 at 14:49 -0500, David Teigland wrote:
> Fix regression in recent patch "[DLM] variable allocation" which
> attempts to dereference an "ls" struct when it's NULL.
>
> Signed-off-by: David Teigland <teigland@redhat.com>
>
> Index: linux-quilt/fs/dlm/rcom.c
> ===================================================================
> --- linux-quilt.orig/fs/dlm/rcom.c 2007-06-06 08:48:33.000000000 -0500
> +++ linux-quilt/fs/dlm/rcom.c 2007-07-13 14:42:19.000000000 -0500
> @@ -386,8 +386,7 @@
> dlm_recover_process_copy(ls, rc_in);
> }
>
> -static int send_ls_not_ready(struct dlm_ls *ls, int nodeid,
> - struct dlm_rcom *rc_in)
> +static int send_ls_not_ready(int nodeid, struct dlm_rcom *rc_in)
> {
> struct dlm_rcom *rc;
> struct rcom_config *rf;
> @@ -395,7 +394,7 @@
> char *mb;
> int mb_len = sizeof(struct dlm_rcom) + sizeof(struct rcom_config);
>
> - mh = dlm_lowcomms_get_buffer(nodeid, mb_len, ls->ls_allocation, &mb);
> + mh = dlm_lowcomms_get_buffer(nodeid, mb_len, GFP_NOFS, &mb);
> if (!mh)
> return -ENOBUFS;
> memset(mb, 0, mb_len);
> @@ -465,7 +464,7 @@
> log_print("lockspace %x from %d type %x not found",
> hd->h_lockspace, nodeid, rc->rc_type);
> if (rc->rc_type == DLM_RCOM_STATUS)
> - send_ls_not_ready(ls, nodeid, rc);
> + send_ls_not_ready(nodeid, rc);
> return;
> }
>
prev parent reply other threads:[~2007-07-16 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 19:49 [Cluster-devel] [PATCH] dlm: fix NULL ls usage David Teigland
2007-07-16 8:48 ` Steven Whitehouse [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=1184575730.8765.303.camel@quoit \
--to=swhiteho@redhat.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 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.