From: David Miller <davem@davemloft.net>
To: damian@tvk.rwth-aachen.de
Cc: rick.jones2@hp.com, ycheng@google.com, netdev@vger.kernel.org
Subject: Re: TCP Connection teardown seems to violate TCP specification
Date: Wed, 14 Aug 2013 17:19:16 -0700 (PDT) [thread overview]
Message-ID: <20130814.171916.338807326839447447.davem@davemloft.net> (raw)
In-Reply-To: <1376515097.9293.6.camel@nexus>
From: Damian Lukowski <damian@tvk.rwth-aachen.de>
Date: Wed, 14 Aug 2013 23:18:17 +0200
> Nevertheless, shouldn't the stack keep on reading the input
> even if the local application is not interested in it?
Absolutely, positively, not.
It is a loss of data, and therefore TCP responds with a reset when
pending read data is not consumed by the application.
next prev parent reply other threads:[~2013-08-15 0:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 19:21 TCP Connection teardown seems to violate TCP specification Damian Lukowski
2013-08-14 19:50 ` Yuchung Cheng
2013-08-14 20:14 ` Rick Jones
2013-08-14 21:18 ` Damian Lukowski
2013-08-14 21:38 ` Rick Jones
2013-08-15 5:32 ` Damian Lukowski
2013-08-15 0:19 ` David Miller [this message]
2013-08-14 20:46 ` Damian Lukowski
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=20130814.171916.338807326839447447.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=damian@tvk.rwth-aachen.de \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=ycheng@google.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 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).