From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH] sparse-checkout: use fdopen_lock_file() instead of xfdopen()
Date: Thu, 05 Sep 2024 14:20:18 -0700 [thread overview]
Message-ID: <xmqqmsklztkd.fsf@gitster.g> (raw)
In-Reply-To: <xmqqr09xztqa.fsf@gitster.g> (Junio C. Hamano's message of "Thu, 05 Sep 2024 14:16:45 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Patrick Steinhardt <ps@pks.im> writes:
>
>>> + 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.
>
> Hmph. Would this be sufficient as a band-aid, then?
Of course not. That would refer to a piece of memory that we
already free'ed in this function.
Perhaps like this?
diff --git a/builtin/sparse-checkout.c b/builtin/sparse-checkout.c
index f1bd31b2f7..27d181a612 100644
--- a/builtin/sparse-checkout.c
+++ b/builtin/sparse-checkout.c
@@ -328,7 +328,7 @@ static int write_patterns_and_update(struct pattern_list *pl)
char *sparse_filename;
FILE *fp;
struct lock_file lk = LOCK_INIT;
- int result;
+ int result = 0;
sparse_filename = get_sparse_checkout_filename();
@@ -336,19 +336,18 @@ static int write_patterns_and_update(struct pattern_list *pl)
die(_("failed to create directory for sparse-checkout file"));
hold_lock_file_for_update(&lk, sparse_filename, LOCK_DIE_ON_ERROR);
- free(sparse_filename);
result = update_working_directory(pl);
if (result) {
rollback_lock_file(&lk);
clear_pattern_list(pl);
update_working_directory(NULL);
- return result;
+ goto out;
}
fp = fdopen_lock_file(&lk, "w");
if (!fp)
- die_errno(_("unable to fdopen %s"), get_lock_file_path(&lk));
+ die_errno(_("unable to fdopen %s"), sparse_filename);
if (core_sparse_checkout_cone)
write_cone_to_file(fp, pl);
@@ -356,11 +355,13 @@ static int write_patterns_and_update(struct pattern_list *pl)
write_patterns_to_file(fp, pl);
if (commit_lock_file(&lk))
- die_errno(_("unable to write %s"), get_locked_file_path(&lk));
+ die_errno(_("unable to write %s"), sparse_filename);
clear_pattern_list(pl);
- return 0;
+out:
+ free(sparse_filename);
+ return result;
}
enum sparse_checkout_mode {
next prev parent reply other threads:[~2024-09-05 21:20 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
2024-09-05 21:16 ` Junio C Hamano
2024-09-05 21:20 ` Junio C Hamano [this message]
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=xmqqmsklztkd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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).