LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Daniel Stempel" <daniel.stempel@inat.de>
To: linux-kernel@vger.kernel.org
Subject: TCP timeout problem
Date: Mon, 19 Feb 2007 15:41:27 +0000 [thread overview]
Message-ID: <0004B32F.45D9D336@192.168.1.132> (raw)
Greetings,
I need some advice concerning tcp-timeout behaviour.
I've got two devices communicating with eachother via TCP. Pulling the network cable from one of these devices interrpts the connection and it should timeout (timeout is set to e.g. 30 seconds). Thats where the problem lies. The connection does not timeout, because the keepalive_timer always gets reset by this piece of code:
:code begin:
/* It is alive without keepalive 8) */
if (tp->packets_out || tp->send_head)
goto resched;
:code end:
(in tcp_timer.c -> tcp_keepalive_timer(unsigned long data))
A timeout never occurs and the connection will not terminate.
What is the reason for this behaviour (what exactly does this code do?) and is there any solution to this. If I delete the above mentioned code, timeout works fine. But changing proven kernel code is no appropriate solution. The kernel version I use is 2.4.18.
Thx in advance
Daniel Stempel
reply other threads:[~2007-02-19 15:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0004B32F.45D9D336@192.168.1.132 \
--to=daniel.stempel@inat.de \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: TCP timeout problem' \
/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
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).