From: Brian Foster <bfoster@redhat.com>
To: Boris Ranto <ranto.boris@gmail.com>
Cc: branto@redhat.com, xfs@oss.sgi.com
Subject: Re: [PATCH v2] xfsdump: Fix memory and fd leak in invutil/stobj.c
Date: Fri, 7 Mar 2014 13:48:12 -0500 [thread overview]
Message-ID: <20140307184812.GA19284@laptop.bfoster> (raw)
In-Reply-To: <1394203962-17080-1-git-send-email-ranto.boris@gmail.com>
On Fri, Mar 07, 2014 at 03:52:42PM +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.
>
> Brian Foster noticed that the function also leaks a file descriptor
> in case the file cannot be fstated. Fixing that, too.
>
> Signed-off-by: Boris Ranto <ranto.boris@gmail.com>
> ---
> invutil/stobj.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/invutil/stobj.c b/invutil/stobj.c
> index 428b419..a74ba0f 100644
> --- a/invutil/stobj.c
> +++ b/invutil/stobj.c
> @@ -578,23 +578,24 @@ 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;
> if (fstat(fd, &sb) < 0) {
> fprintf(stderr, "Could not get stat info on %s\n", StObjFileName);
> perror("fstat");
> + close(fd);
> return -1;
> }
> 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);
> }
>
The remaining failure cases all appear to exit(), including those in
add_stobj(). Looks good to me, thanks for making that fix...
Reviewed-by: Brian Foster <bfoster@redhat.com>
> --
> 1.9.0
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2014-03-07 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 14:52 [PATCH v2] xfsdump: Fix memory and fd leak in invutil/stobj.c Boris Ranto
2014-03-07 18:48 ` Brian Foster [this message]
2014-03-11 13:55 ` Boris Ranto
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=20140307184812.GA19284@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