From: Gerrit Renker <gerrit@erg.abdn.ac.uk>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH][RFC] tcp: fix ambiguity in the `before' relation
Date: Thu, 21 Dec 2006 14:42:38 +0000 [thread overview]
Message-ID: <200612211442.38493@strip-the-willow> (raw)
In-Reply-To: <20061220.103112.85414445.davem@davemloft.net>
Hi David,
many thanks for taking the matter seriously and investigating
it further.
| I went over this patch and analysis a dozen times, because I
| couldn't believe something like this has been broken for
| so long :-)
It gave me some grief too, when I looked at DCCP sequence numbers %-)
RFC 1982 provides some definitions, but leaves the case a = (b + 2^31) % 2^32
open to the implementation (suggests `undefined').
I think the new definition is more conformant with RFC 1982 than the old one,
since the ambiguity is now removed with regard to a = (b + 2^31) % 32, and it
is not "unnecessarily burdensome to implement" (section 3.2 of RFC 1982).
| Even BSD suffers of this issue, since the beginning. See
| SEQ_LT() in tcp_seq.h, and it seems that BSD's timestamp
| sequence checking has the issue too (see TSTMP_LT() macro
| in OpenBSD's tcp_input.c)
I didn't know about OpenBSD, but in Stevens vol 2 (sec. 24.7) it is
already defined in this way.
Best regards & merry Christmas
Gerrit
next prev parent reply other threads:[~2006-12-21 14:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 15:07 [PATCH][RFC] tcp: fix ambiguity in the `before' relation Gerrit Renker
2006-12-20 18:31 ` David Miller
2006-12-21 14:42 ` Gerrit Renker [this message]
2006-12-22 0:53 ` Herbert Xu
2007-01-03 8:56 ` Gerrit Renker
2007-01-04 0:15 ` Herbert Xu
2007-01-04 12:49 ` Gerrit Renker
2007-01-05 3:59 ` Herbert Xu
2007-01-05 11:51 ` Gerrit Renker
2007-01-05 12:01 ` Herbert Xu
2007-01-05 12:49 ` Gerrit Renker
2007-01-05 20:34 ` Herbert Xu
2007-01-08 8:58 ` Gerrit Renker
2006-12-20 20:01 ` Christoph Hellwig
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=200612211442.38493@strip-the-willow \
--to=gerrit@erg.abdn.ac.uk \
--cc=davem@davemloft.net \
--cc=netdev@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).