]> err.no Git - linux-2.6/commit
projects / linux-2.6 / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 95eacd2) | patch
[TCP]: Update comment of SACK block validator
authorIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
Mon, 1 Oct 2007 22:28:17 +0000 (15:28 -0700)
committerDavid S. Miller <davem@sunset.davemloft.net>
Wed, 10 Oct 2007 23:53:59 +0000 (16:53 -0700)
commit0e835331e3111e5a92eb3a852405ea71ca8fff97
treee7c1445866cf4ed306ffd39e1fd520f2b761566atree | snapshot
parent95eacd27e2a0924f1435654c06712cee6be099adcommit | diff
[TCP]: Update comment of SACK block validator

Just came across what RFC2018 states about generation of valid
SACK blocks in case of reneging. Alter comment a bit to point
out clearly.

IMHO, there isn't any reason to change code because the
validation is there for a purpose (counters will inform user
about decision TCP made if this case ever surfaces).

Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/ipv4/tcp_input.c diff | blob | history
Linux 2.6 source tree