From: Thomas Rast <trast@student.ethz.ch>
To: "Martin Ettl" <ettl.martin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: found a resource leak in file builtin-fast-export.c
Date: Thu, 9 Jul 2009 10:31:37 +0200 [thread overview]
Message-ID: <200907091031.43494.trast@student.ethz.ch> (raw)
In-Reply-To: <20090709075728.137880@gmx.net>
[-- Attachment #1: Type: Text/Plain, Size: 880 bytes --]
Hi Martin
Martin Ettl wrote:
>
> I have attached a patch to resolve this.
Please read Documentation/SubmittingPatches in the source tree. And
use git to track git.git!
As for the actual patch:
> --- git-1.6.3.3/builtin-fast-export.c 2009-06-22 08:24:25.000000000 +0200
> +++ git-1.6.3.3/builtin-fast-export_new.c 2009-07-09 09:44:28.000000000 +0200
> @@ -442,8 +442,9 @@ static void export_marks(char *file)
> deco++;
> }
>
> - if (ferror(f) || fclose(f))
> + if (ferror(f))
> error("Unable to write marks file %s.", file);
> + fclose(f);
You no longer check the error returned by fclose(). This is
important, because the FILE* API may buffer writes, and a write error
may only become apparent when fclose() flushes the file.
> }
>
> static void import_marks(char *input_file)
--
Thomas Rast
trast@{inf,student}.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-07-09 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 7:57 found a resource leak in file builtin-fast-export.c Martin Ettl
2009-07-09 8:31 ` Thomas Rast [this message]
2009-07-09 11:04 ` Johannes Schindelin
2009-07-09 11:24 ` Thomas Rast
2009-07-09 11:30 ` Andreas Ericsson
2009-07-09 13:01 ` Johannes Schindelin
2009-07-09 13:28 ` [PATCH] Fix export_marks() error handling Matthias Andree
2009-07-11 9:45 ` Stephen R. van den Berg
2009-07-13 8:01 ` Matthias Andree
2009-07-09 13:36 ` found a resource leak in file builtin-fast-export.c Matthias Andree
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=200907091031.43494.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=ettl.martin@gmx.de \
--cc=git@vger.kernel.org \
/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.