From: Matthias Lederhofer <matled@gmx.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] upload-pack: fix timeout in create_pack_file
Date: Mon, 24 Jul 2006 09:10:12 +0200 [thread overview]
Message-ID: <E1G4uZw-0006vZ-VO@moooo.ath.cx> (raw)
In-Reply-To: <7vd5bvh67p.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> > This does not help for low timeouts with slow clients. If a client is
> > slow enough so the server is blocked for more time than specified by
> > timeout the connection will be closed too (e.g. 15kb/s with a timeout
> > of 30 (git adds 10 extra) is not enough).
>
> Where do we add 10 extra?
Oops, never mind, I misread the source.
> > We should either add a
> > warning to the man page or try to fix this. I don't know if this can
> > be fixed not using non-blocking sockets.
>
> I think the intent of "timeout" was to protect us from funny
> clients by avoiding talking with the ones that take too much
> time doing something that should not take too long. When we are
> in create_pack_file(), we are already committed to the heaviest
> operation anyway, so one possibility might be to stop doing
> timeout at that point. I am not sure if that is acceptable,
> though -- it opens up the daemon to even easier DoS than it
> currently is.
>
> My gut feeling is that your patch would be fine as is (have you
> tried and confirmed that it helps cases other than slow
> clients?)
What else? The problem solved by this patch is the missing
reset_timeout while downloading pack files and this affects all
clients that are too slow (cannot download the packfile within
--timeout seconds). I tried a server with --timeout=600 and a client
that cannot download the whole pack file in 10 minutes. Without the
patch the server closes the connection, with this patch it works.
Additionally I tried it with a client reading so slow that the server
was blocked for more than --timeout seconds, then the server closes
the connection too (this is more or less the DoS case).
> > Perhaps support for resume would be quite useful too but I've no idea
> > how hard this is to implement.
>
> That would be _very_ hard.
I don't know how much demand there is for resuming but there is always rsync
(at least on kernel.org and other repositories that need it can install it too)
to get the new objects with support for resuming.
next prev parent reply other threads:[~2006-07-24 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 17:14 [PATCH] upload-pack: fix timeout in create_pack_file Matthias Lederhofer
2006-07-24 6:23 ` Junio C Hamano
2006-07-24 7:10 ` Matthias Lederhofer [this message]
2006-07-24 7:55 ` 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=E1G4uZw-0006vZ-VO@moooo.ath.cx \
--to=matled@gmx.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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