From: Holger Freyther <zecke@selfish.org>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org
Subject: Re: Unable to clone via git protocol / early EOF / index-pack failed
Date: Sat, 26 Mar 2011 19:50:41 +0100 [thread overview]
Message-ID: <4D8E3581.6020003@selfish.org> (raw)
In-Reply-To: <vpq8vw1epc1.fsf@bauges.imag.fr>
On 03/26/2011 06:58 PM, Matthieu Moy wrote:
>
> That reminds me an issue I had with git over SSH. The problem was indeed
> not Git-related:
>
> http://readlist.com/lists/securityfocus.com/secureshell/0/3071.html
>
> In short, when sending 196481 bytes or more, _and_ if the server did not
> consume the data fast enough, then the connection was closed after
> 65536=2^16 bytes.
>
> That was on RHEL, and upgrading the kernel solved the issue. Scary...
>
Yes, scary. I assume that fflush(stdout) has no real meaning for sockets
either? So the next best thing would be to use ioctl and SIOCOUTQ on the
socket? Any other ideas?
prev parent reply other threads:[~2011-03-26 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 10:27 Unable to clone via git protocol / early EOF / index-pack failed Harald Welte
2011-03-24 10:30 ` Harald Welte
2011-03-26 17:12 ` Holger Freyther
2011-03-26 17:34 ` Holger Freyther
2011-03-26 17:58 ` Matthieu Moy
2011-03-26 18:50 ` Holger Freyther [this message]
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=4D8E3581.6020003@selfish.org \
--to=zecke@selfish.org \
--cc=Matthieu.Moy@grenoble-inp.fr \
--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).