From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stefan Beller <sbeller@google.com>,
sunshine@sunshineco.com, git@vger.kernel.org
Subject: Re: [PATCHv4 3/4] bundle: don't leak an fd in case of early return
Date: Fri, 1 Apr 2016 13:31:09 -0400 [thread overview]
Message-ID: <20160401173109.GA21061@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqk2khi6eo.fsf@gitster.mtv.corp.google.com>
On Fri, Apr 01, 2016 at 10:29:51AM -0700, Junio C Hamano wrote:
> > This does still suffer from the double-close I mentioned earlier. I'm
> > not sure if we want to address that or not.
>
> Something like this on top?
>
> bundle.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/bundle.c b/bundle.c
> index 08e32ca..bbf4efa 100644
> --- a/bundle.c
> +++ b/bundle.c
> @@ -453,8 +453,10 @@ int create_bundle(struct bundle_header *header, const char *path,
> goto err;
>
> /* write pack */
> - if (write_pack_data(bundle_fd, &revs))
> + if (write_pack_data(bundle_fd, &revs)) {
> + bundle_fd = -1; /* already closed by the above call */
> goto err;
> + }
>
> if (!bundle_to_stdout) {
> if (commit_lock_file(&lock))
> @@ -463,7 +465,8 @@ int create_bundle(struct bundle_header *header, const char *path,
> return 0;
> err:
> if (!bundle_to_stdout) {
> - close(bundle_fd);
> + if (0 <= bundle_fd)
> + close(bundle_fd);
> rollback_lock_file(&lock);
Yep, that looks fine.
-Peff
next prev parent reply other threads:[~2016-04-01 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 0:35 [PATCHv4 0/4] Some cleanups Stefan Beller
2016-04-01 0:35 ` [PATCHv4 1/4] notes: don't leak memory in git_config_get_notes_strategy Stefan Beller
2016-04-01 0:46 ` Eric Sunshine
2016-04-01 16:12 ` Junio C Hamano
2016-04-01 17:03 ` Junio C Hamano
2016-04-01 17:14 ` Jeff King
2016-04-01 17:30 ` Eric Sunshine
2016-04-01 0:35 ` [PATCHv4 2/4] abbrev_sha1_in_line: don't leak memory Stefan Beller
2016-04-01 0:35 ` [PATCHv4 3/4] bundle: don't leak an fd in case of early return Stefan Beller
2016-04-01 17:05 ` Junio C Hamano
2016-04-01 17:15 ` Jeff King
2016-04-01 17:29 ` Junio C Hamano
2016-04-01 17:31 ` Jeff King [this message]
2016-04-01 0:35 ` [PATCHv4 4/4] credential-cache, send_request: close fd when done Stefan Beller
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=20160401173109.GA21061@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.com \
--cc=sunshine@sunshineco.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;
as well as URLs for NNTP newsgroup(s).