From: David Rothenberger <daveroth@acm.org>
To: git@vger.kernel.org
Subject: Re: [PATCH v3 1/2] Git.pm: add new temp_is_locked function
Date: Thu, 18 Jul 2013 18:34:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20130718T202918-857@post.gmane.org> (raw)
In-Reply-To: 1373170849-9150-2-git-send-email-mackyle@gmail.com
Kyle J. McKay <mackyle <at> gmail.com> writes:
> +sub temp_is_locked {
> + my ($self, $name) = _maybe_self( <at> _);
> + my $temp_fd = \$TEMP_FILEMAP{$name};
> +
> + defined $$temp_fd && $$temp_fd->opened && $TEMP_FILES{$$temp_fd}{locked};
> +}
> +
> =item temp_release ( NAME )
>
> =item temp_release ( FILEHANDLE )
> <at> <at> -1248,7 +1277,7 <at> <at> sub _temp_cache {
>
> my $temp_fd = \$TEMP_FILEMAP{$name};
> if (defined $$temp_fd and $$temp_fd->opened) {
> - if ($TEMP_FILES{$$temp_fd}{locked}) {
> + if (temp_is_locked($name)) {
> throw Error::Simple("Temp file with moniker '" .
> $name . "' already in use");
> }
There's a problem with this use of temp_is_locked. There is an else
clause right after this:
} else {
if (defined $$temp_fd) {
# then we're here because of a closed handle.
Prior to the patch, the comment is correct, but after the patch, the
if block may also be entered if the file is open but locked. This is
because temp_is_locked checks that the temp file is defined, open,
and locked.
This issue leads to lots of
Temp file 'svn_delta_3360_0' was closed. Opening replacement.
messages for me.
Reverting the change in _temp_cache solves the problem for me.
Adding an " && !$$temp_fd->opened" clause to the if statement also
works, but this is less efficient.
next prev parent reply other threads:[~2013-07-18 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 4:20 [PATCH v3 0/2] allow git-svn fetching to work using serf Kyle J. McKay
2013-07-07 4:20 ` [PATCH v3 1/2] Git.pm: add new temp_is_locked function Kyle J. McKay
2013-07-18 18:34 ` David Rothenberger [this message]
2013-07-18 19:14 ` Kyle J. McKay
2013-07-18 19:35 ` Jonathan Nieder
2013-07-07 4:20 ` [PATCH v3 2/2] git-svn: allow git-svn fetching to work using serf Kyle J. McKay
2013-07-08 16:22 ` [PATCH v3 0/2] " Junio C Hamano
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=loom.20130718T202918-857@post.gmane.org \
--to=daveroth@acm.org \
--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 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).