Subject: Re: [PATCH v5] lockfile: add PID file for debugging stale locks

From: Junio C Hamano <[email-masked]>
Date: Wed, 21 Jan 2026 08:23:50 -0800

Jeff King <[email-masked]> writes:

> I don't think it's wrong, but the cleanup is redundant between the "out"
> path and the others.
>
> Did you mean this:
>
> diff --git a/lockfile.c b/lockfile.c
> index 731cdd4944..e5d6ae0df6 100644
> --- a/lockfile.c
> +++ b/lockfile.c
> @@ -122,14 +122,10 @@ static struct tempfile *create_lock_pid_file(const char *pid_path, int mode)
>  	strbuf_addf(&content, "pid %" PRIuMAX "\n", (uintmax_t)getpid());
>  	if (write_in_full(fd, content.buf, content.len) < 0) {
>  		warning_errno(_("could not write lock pid file '%s'"), pid_path);
> -		close(fd);
> -		fd = -1;
>  		unlink(pid_path);
>  		goto out;
>  	}
>  
> -	close(fd);
> -	fd = -1;
>  	pid_tempfile = register_tempfile(pid_path);
>  
>  out:
>
> which would just let the close after the out label handle all cases?

I recall suggesting this myself in

https://lore.kernel.org/git/[email-masked]

without realizing that this would probably not work on Windows where
unlink() cannot work correctly until the file descriptor is closed.