From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] sparse-checkout: use fdopen_lock_file() instead of xfdopen()
Date: Thu, 5 Sep 2024 12:54:42 +0200 [thread overview]
Message-ID: <ZtmN6sZCvDy1BGfn@pks.im> (raw)
In-Reply-To: <20240905082749.GA88220@coredump.intra.peff.net>
On Thu, Sep 05, 2024 at 04:27:49AM -0400, Jeff King wrote:
> diff --git a/builtin/sparse-checkout.c b/builtin/sparse-checkout.c
> index 2604ab04df..f1bd31b2f7 100644
> --- a/builtin/sparse-checkout.c
> +++ b/builtin/sparse-checkout.c
> @@ -336,8 +335,7 @@ static int write_patterns_and_update(struct pattern_list *pl)
> if (safe_create_leading_directories(sparse_filename))
> die(_("failed to create directory for sparse-checkout file"));
>
> - fd = hold_lock_file_for_update(&lk, sparse_filename,
> - LOCK_DIE_ON_ERROR);
> + hold_lock_file_for_update(&lk, sparse_filename, LOCK_DIE_ON_ERROR);
> free(sparse_filename);
>
> result = update_working_directory(pl);
Okay, we die on an error so there is no need to check `fd`, either.
Makes sense.
> @@ -348,15 +346,17 @@ static int write_patterns_and_update(struct pattern_list *pl)
> return result;
> }
>
> - fp = xfdopen(fd, "w");
> + fp = fdopen_lock_file(&lk, "w");
> + if (!fp)
> + die_errno(_("unable to fdopen %s"), get_lock_file_path(&lk));
>
> if (core_sparse_checkout_cone)
> write_cone_to_file(fp, pl);
> else
> write_patterns_to_file(fp, pl);
>
> - fflush(fp);
> - commit_lock_file(&lk);
> + if (commit_lock_file(&lk))
> + die_errno(_("unable to write %s"), get_locked_file_path(&lk));
>
> clear_pattern_list(pl);
I think the error handling is broken. `commit_lock_file()` calls
`rename_tempfile()`, which deletes the temporary file even in the error
case. The consequence is that `lk->tempfile` will be set to the `NULL`
pointer. When we call `get_locked_file_path()` we then dereference it
unconditionally and would thus segfault.
Other than that this patch looks sensible. Also kind of curious that we
never checked that `commit_lock_file()` was successful, so we wouldn't
even notice when renaming the file into place failed.
Patrick
next prev parent reply other threads:[~2024-09-05 10:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 8:27 [PATCH] sparse-checkout: use fdopen_lock_file() instead of xfdopen() Jeff King
2024-09-05 10:54 ` Patrick Steinhardt [this message]
2024-09-05 21:16 ` Junio C Hamano
2024-09-05 21:20 ` Junio C Hamano
2024-09-06 1:19 ` Jeff King
2024-09-06 14:55 ` Junio C Hamano
2024-09-05 15:16 ` Junio C Hamano
2024-09-06 3:45 ` [PATCH v2 0/3] sparse-checkout file handle leak fix Jeff King
2024-09-06 3:47 ` [PATCH v2 1/3] sparse-checkout: consolidate cleanup when writing patterns Jeff King
2024-09-06 3:47 ` [PATCH v2 2/3] sparse-checkout: check commit_lock_file " Jeff King
2024-09-06 3:48 ` [PATCH v2 3/3] sparse-checkout: use fdopen_lock_file() instead of xfdopen() Jeff King
2024-09-06 9:25 ` [PATCH v2 0/3] sparse-checkout file handle leak fix Patrick Steinhardt
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=ZtmN6sZCvDy1BGfn@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).