From: Junio C Hamano <gitster@pobox.com>
To: "Uli Heller" <uli.heller@daemons-point.com>
Cc: "Kyle J. McKay" <mackyle@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Eric Wong" <normalperson@yhbt.net>
Subject: Re: [PATCH] git-svn: Fix termination issues for remote svn connections
Date: Fri, 06 Sep 2013 09:41:15 -0700 [thread overview]
Message-ID: <xmqqa9jpzyvo.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <f2fe486a6ca0bf40be4489bfe888d517.squirrel@83.236.132.106> (Uli Heller's message of "Fri, 6 Sep 2013 15:18:32 +0200 (CEST)")
"Uli Heller" <uli.heller@daemons-point.com> writes:
> On Fri, September 6, 2013 2:44 pm, Kyle J. McKay wrote:
> ...
>> In any case, I can now reproduce the problem (serf 1.3.1 still breaks
>> since it does not yet contain the fix and it is the most recent serf
>> release available).
>>
>> And the Git/SVN/Ra.pm fix does eliminate the problem for me (both with
>> bulk updates and with skelta updates -- the crash occurs with either).
>
> Great. So I don't have to run any more tests ;)
>
> What shall I do next? Add some inline comments to the patch?
Something like this?
-- >8 --
From: Uli Heller <uli.heller@daemons-point.com>
Subject: [PATCH] git-svn: fix termination issues for remote svn connections
git-svn used in combination with serf to talk to svn repository
served over HTTPS dumps core on termination.
This is caused by a bug in serf, and the most recent serf release
1.3.1 still exhibits the problem; a fix for the bug exists (see
https://code.google.com/p/serf/source/detail?r=2146).
Until the bug is fixed, work around the issue within the git perl
module Ra.pm by freeing the private copy of the remote access object
on termination, which seems to be sufficient to prevent the error
from happening.
Note: Since subversion-1.8.0 and later do require serf-1.2.1 or
later, this issue typically shows up when upgrading to a recent
version of subversion.
Credits go to Jonathan Lambrechts for proposing a fix to Ra.pm,
Evgeny Kotkov and Ivan Zhakov for fixing the issue in serf and
pointing me to that fix.
Signed-off-by: Uli Heller <uli.heller@daemons-point.com>
Tested-by: Kyle J. McKay <mackyle@gmail.com>
---
perl/Git/SVN/Ra.pm | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/perl/Git/SVN/Ra.pm b/perl/Git/SVN/Ra.pm
index 75ecc42..78dd346 100644
--- a/perl/Git/SVN/Ra.pm
+++ b/perl/Git/SVN/Ra.pm
@@ -32,6 +32,14 @@ BEGIN {
}
}
+# serf has a bug that leads to a coredump upon termination if the
+# remote access object is left around (not fixed yet in serf 1.3.1).
+# Explicitly free it to work around the issue.
+END {
+ $RA = undef;
+ $ra_invalid = 1;
+}
+
sub _auth_providers () {
my @rv = (
SVN::Client::get_simple_provider(),
--
1.8.4-431-g94f3a6b
next prev parent reply other threads:[~2013-09-06 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 7:35 [PATCH] git-svn: Fix termination issues for remote svn connections Uli Heller
2013-09-05 18:48 ` Junio C Hamano
2013-09-05 19:02 ` Eric Wong
2013-09-05 23:14 ` Junio C Hamano
2013-09-06 11:46 ` Kyle J. McKay
2013-09-06 12:06 ` Uli Heller
2013-09-06 12:44 ` Kyle J. McKay
2013-09-06 13:18 ` Uli Heller
2013-09-06 16:41 ` Junio C Hamano [this message]
2013-09-09 6:01 ` [PATCH v2] " Uli Heller
2013-09-09 15:42 ` Junio C Hamano
2013-09-06 12:44 ` [PATCH] " Kyle J. McKay
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=xmqqa9jpzyvo.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mackyle@gmail.com \
--cc=normalperson@yhbt.net \
--cc=uli.heller@daemons-point.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.