Remove a KASSERT in the sack path that fails because of a interaction

between sack and a bug in the "bad retransmit recovery" logic. This is
a workaround, the underlying bug will be fixed later.

Submitted by:   Mohan Srinivasan, Noritoshi Demizu
This commit is contained in:
Paul Saab 2005-08-24 02:48:45 +00:00
parent b24de0e665
commit 4d3b134633
2 changed files with 0 additions and 6 deletions

View File

@ -1917,9 +1917,6 @@ trimthenstep6:
callout_stop(tp->tt_rexmt);
tp->t_rtttime = 0;
if (tp->sack_enable) {
KASSERT(tp->sackhint.
sack_bytes_rexmit == 0,
("sackhint rexmit == 0"));
tcpstat.tcps_sack_recovery_episode++;
tp->sack_newdata = tp->snd_nxt;
tp->snd_cwnd = tp->t_maxseg;

View File

@ -1917,9 +1917,6 @@ trimthenstep6:
callout_stop(tp->tt_rexmt);
tp->t_rtttime = 0;
if (tp->sack_enable) {
KASSERT(tp->sackhint.
sack_bytes_rexmit == 0,
("sackhint rexmit == 0"));
tcpstat.tcps_sack_recovery_episode++;
tp->sack_newdata = tp->snd_nxt;
tp->snd_cwnd = tp->t_maxseg;