From: Brian Foster <bfoster@redhat.com>
To: Boris Ranto <ranto.boris@gmail.com>
Cc: branto@redhat.com, xfs@oss.sgi.com
Subject: Re: [PATCH] xfsdump: Fix memory leak in invutil/stobj.c
Date: Thu, 6 Mar 2014 12:23:56 -0500 [thread overview]
Message-ID: <20140306172356.GB11842@laptop.bfoster> (raw)
In-Reply-To: <1394050311-17965-1-git-send-email-ranto.boris@gmail.com>
On Wed, Mar 05, 2014 at 09:11:51PM +0100, Boris Ranto wrote:
> The function open_stobj duplicates its argument, upon successful
> duplication, the fstat is called. If the fstat command fails then
> the memory for the duplicated string is leaked. Fix this by moving
> the string duplication after the fstat call. This is ok because
> the fstat call does not use the duplicated string.
>
> Signed-off-by: Boris Ranto <ranto.boris@gmail.com>
> ---
The fix looks fine to me, but in the same scenario it looks like we also
leak the fd. Care to clean that up in this patch as well? :)
Brian
> invutil/stobj.c | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/invutil/stobj.c b/invutil/stobj.c
> index 428b419..55abe63 100644
> --- a/invutil/stobj.c
> +++ b/invutil/stobj.c
> @@ -578,12 +578,6 @@ open_stobj(char *StObjFileName)
> return fd;
> }
>
> - name = strdup(StObjFileName);
> - if(name == NULL) {
> - fprintf(stderr, "%s: internal memory error: strdup stobj_name\n", g_programName);
> - exit(1);
> - }
> -
> read_n_bytes(fd, &cnt, sizeof(invt_sescounter_t), StObjFileName);
> lseek( fd, 0, SEEK_SET );
> errno = 0;
> @@ -595,6 +589,12 @@ open_stobj(char *StObjFileName)
> size = sb.st_size;
> mapaddr = mmap_n_bytes(fd, size, BOOL_FALSE, StObjFileName);
>
> + name = strdup(StObjFileName);
> + if(name == NULL) {
> + fprintf(stderr, "%s: internal memory error: strdup stobj_name\n", g_programName);
> + exit(1);
> + }
> +
> return add_stobj(name, fd, size, mapaddr, (invt_sescounter_t *)mapaddr);
> }
>
> --
> 1.7.1
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-03-06 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 20:11 [PATCH] xfsdump: Fix memory leak in invutil/stobj.c Boris Ranto
2014-03-06 17:23 ` Brian Foster [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=20140306172356.GB11842@laptop.bfoster \
--to=bfoster@redhat.com \
--cc=branto@redhat.com \
--cc=ranto.boris@gmail.com \
--cc=xfs@oss.sgi.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