[<prev] [next>] [day] [month] [year] [list]
Message-Id: <200702100211.l1A2BPFG007255@igsi.llnl.gov>
Date: Fri, 9 Feb 2007 18:11:25 -0800
From: "Brian D. Behlendorf" <behlendorf1@...l.gov>
To: tytso@....edu
Cc: linux-ext4@...r.kernel.org, adilger@...sterfs.com,
behlendorf1@...l.gov, wartens2@...l.gov
Subject: e2fsprogs coverity patch <cid-29.diff>
Lawrence Livermore National Labs recently ran the source code
analysis tool Coverity over the e2fsprogs-1.39 source to see
if it would identify any significant bugs. The analysis
turned up 38 mostly minor issues which are enumerated here
with patches. We went through and resolved these issues
but would love to see these mostly minor changes reviewed
and commited upstream.
Thanks,
Brian Behlendorf <behlendorf1@...l.gov>, and
Herb Wartens <wartens2@...l.gov>
-----------------------------------------------------------------------------
Coverity ID: 29: Resource Leak
name is allocated some memory in blkid_strndup. We could
potentially exit parse_dev() early if blkid_get_dev() is
unable to allocate memory. blkid_get_dev() is passed name
but the address of name is not copied (instead a "deep" copy
is made in the form of strdup). Thus it should be perfectly safe
to free name in this early return.
Index: e2fsprogs+chaos/lib/blkid/read.c
===================================================================
--- e2fsprogs+chaos.orig/lib/blkid/read.c
+++ e2fsprogs+chaos/lib/blkid/read.c
@@ -182,7 +182,7 @@ static int parse_end(char **cp)
*/
static int parse_dev(blkid_cache cache, blkid_dev *dev, char **cp)
{
- char *start, *tmp, *end, *name;
+ char *start, *tmp, *end, *name = NULL;
int ret;
if ((ret = parse_start(cp)) <= 0)
@@ -223,8 +223,10 @@ static int parse_dev(blkid_cache cache,
DBG(DEBUG_READ, printf("found dev %s\n", name));
- if (!(*dev = blkid_get_dev(cache, name, BLKID_DEV_CREATE)))
+ if (!(*dev = blkid_get_dev(cache, name, BLKID_DEV_CREATE))) {
+ free(name);
return -BLKID_ERR_MEM;
+ }
free(name);
return 1;
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists