diff options
author | Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> | 2007-10-02 00:28:17 +0200 |
---|---|---|
committer | David S. Miller <davem@sunset.davemloft.net> | 2007-10-11 01:53:59 +0200 |
commit | 0e835331e3111e5a92eb3a852405ea71ca8fff97 (patch) | |
tree | e7c1445866cf4ed306ffd39e1fd520f2b761566a /net/ipv4/esp4.c | |
parent | [TCP]: fix comments that got messed up during code move (diff) | |
download | linux-0e835331e3111e5a92eb3a852405ea71ca8fff97.tar.xz linux-0e835331e3111e5a92eb3a852405ea71ca8fff97.zip |
[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>
Diffstat (limited to 'net/ipv4/esp4.c')
0 files changed, 0 insertions, 0 deletions