From: Jim Meyering <jim@meyering.net>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH cluster 2/5] dlm_controld: handle heap allocation failure and plug leaks
Date: Thu, 25 Jun 2009 22:29:43 +0200 [thread overview]
Message-ID: <87d48s9hvs.fsf@meyering.net> (raw)
In-Reply-To: <1245757450-13840-3-git-send-email-jim@meyering.net> (Jim Meyering's message of "Tue, 23 Jun 2009 13:44:07 +0200")
Jim Meyering wrote:
> From: Jim Meyering <meyering@redhat.com>
>
> * group/dlm_controld/pacemaker.c (process_cluster): Don't dereference
> NULL upon failing malloc or realloc. Free "header" upon failure.
> ---
> group/dlm_controld/pacemaker.c | 16 +++++++++++-----
> 1 files changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/group/dlm_controld/pacemaker.c b/group/dlm_controld/pacemaker.c
> index fed9ca7..b9b38d0 100644
> --- a/group/dlm_controld/pacemaker.c
> +++ b/group/dlm_controld/pacemaker.c
> @@ -135,10 +135,12 @@ void process_cluster(int ci)
>
> AIS_Message *msg = NULL;
> SaAisErrorT rc = SA_AIS_OK;
> - mar_res_header_t *header = NULL;
> + mar_res_header_t *header;
> + mar_res_header_t *h;
Oops. That "h" have been "h_new".
(Andrew Beekhof noticed this)
...
> + h_new = realloc(header, header->size);
Here's the corrected patch:
From bbc3ffcaf72d8089a1783af8ec9dc5b726a2b68e Mon Sep 17 00:00:00 2001
From: Jim Meyering <meyering@redhat.com>
Date: Mon, 22 Jun 2009 23:37:21 +0200
Subject: [PATCH cluster] dlm_controld: handle heap allocation failure and plug leaks
* group/dlm_controld/pacemaker.c (process_cluster): Don't dereference
NULL upon failing malloc or realloc. Free "header" upon failure.
---
group/dlm_controld/pacemaker.c | 16 +++++++++++-----
1 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/group/dlm_controld/pacemaker.c b/group/dlm_controld/pacemaker.c
index 509696a..9b0a2d8 100644
--- a/group/dlm_controld/pacemaker.c
+++ b/group/dlm_controld/pacemaker.c
@@ -135,10 +135,12 @@ void process_cluster(int ci)
AIS_Message *msg = NULL;
SaAisErrorT rc = SA_AIS_OK;
- mar_res_header_t *header = NULL;
+ mar_res_header_t *header;
+ mar_res_header_t *h_new;
static int header_len = sizeof(mar_res_header_t);
- header = malloc(header_len);
+ if ((header = malloc(header_len)) == NULL)
+ goto bail;
memset(header, 0, header_len);
errno = 0;
@@ -160,8 +162,12 @@ void process_cluster(int ci)
} else if(header->error != 0) {
log_error("Header contined error: %d", header->error);
}
-
- header = realloc(header, header->size);
+
+ h_new = realloc(header, header->size);
+ if (h_new == NULL)
+ goto bail;
+ header = h_new;
+
/* Use a char* so we can store the remainder into an offset */
data = (char*)header;
@@ -252,6 +258,7 @@ void process_cluster(int ci)
goto done;
bail:
+ free (header);
log_error("AIS connection failed");
return;
}
@@ -408,4 +415,3 @@ int fence_in_progress(int *count)
{
return 0;
}
-
--
1.6.3.3.420.gd4b46
next prev parent reply other threads:[~2009-06-25 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 11:44 [Cluster-devel] [PATCH cluster 0/5] NULL-deref after failed malloc (STABLE3) Jim Meyering
2009-06-23 11:44 ` [Cluster-devel] [PATCH cluster 1/5] src/clulib/ckpt_state.c (ds_key_init_nt): detect failed malloc Jim Meyering
2009-06-23 11:44 ` [Cluster-devel] [PATCH cluster 2/5] dlm_controld: handle heap allocation failure and plug leaks Jim Meyering
2009-06-25 20:29 ` Jim Meyering [this message]
2009-06-23 11:44 ` [Cluster-devel] [PATCH cluster 3/5] dlm_controld: add comments: mark memory problems Jim Meyering
2009-06-23 11:44 ` [Cluster-devel] [PATCH cluster 4/5] dlm/tests: handle malloc failure Jim Meyering
2009-06-23 11:44 ` [Cluster-devel] [PATCH cluster 5/5] cman: handle malloc failure (i.e., don't deref NULL) Jim Meyering
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=87d48s9hvs.fsf@meyering.net \
--to=jim@meyering.net \
/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