git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "Kyle J. McKay" <mackyle@gmail.com>
To: David Rothenberger <daveroth@acm.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3 1/2] Git.pm: add new temp_is_locked function
Date: Thu, 18 Jul 2013 12:14:47 -0700	[thread overview]
Message-ID: <842D3E63-9E6B-45F0-A7F6-03082C4D067F@gmail.com> (raw)
In-Reply-To: <loom.20130718T202918-857@post.gmane.org>

On Jul 18, 2013, at 11:34, David Rothenberger wrote:
> 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.

That change was made as a result of this feedback:

On Jul 6, 2013, at 17:11, Jonathan Nieder wrote:
> Hi,
>
> Kyle McKay wrote:
>
>> The temp_is_locked function can be used to determine whether
>> or not a given name previously passed to temp_acquire is
>> currently locked.
> [...]
>> +=item temp_is_locked ( NAME )
>> +
>> +Returns true if the file mapped to C<NAME> is currently locked.
>> +
>> +If true is returned, an attempt to C<temp_acquire()> the same
>
[snip]
>
> Looking more closely, it looks like this is factoring out the idiom
> for checking if a name is already in use from the _temp_cache
> function.  Would it make sense for _temp_cache to call this helper?

So I think the answer is it does not make sense for _temp_cache to  
call this helper.

Will release a v4 in just a moment with that single change reverted.

  reply	other threads:[~2013-07-18 19:15 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
2013-07-18 19:14     ` Kyle J. McKay [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=842D3E63-9E6B-45F0-A7F6-03082C4D067F@gmail.com \
    --to=mackyle@gmail.com \
    --cc=daveroth@acm.org \
    --cc=git@vger.kernel.org \
    --subject='Re: [PATCH v3 1/2] Git.pm: add new temp_is_locked function' \
    /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

git@vger.kernel.org list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ https://public-inbox.org/git \
		git@vger.kernel.org
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/inbox.comp.version-control.git
	nntp://ie5yzdi7fg72h7s4sdcztq5evakq23rdt33mfyfcddc5u3ndnw24ogqd.onion/inbox.comp.version-control.git
	nntp://4uok3hntl7oi7b4uf4rtfwefqeexfzil2w6kgk2jn5z2f764irre7byd.onion/inbox.comp.version-control.git
	nntp://news.gmane.io/gmane.comp.version-control.git
 note: .onion URLs require Tor: https://www.torproject.org/

code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git