Re: Computed sack_bytes_retransmitted (x) not the same as cached value

This was fixed on June 6. Can you pick up the latest changes ?
There were other TCP and SACK fixes checked in since Jun 5.

This is the change you need for the bug you report.

Revision 1.22 / (download) - annotate - [select for diffs], Mon Jun 6 19:46:53 2005 UTC (5 weeks,
2 days ago) by ps
Branch: MAIN
Changes since 1.21: +9 -4 lines
Diff to previous 1.21 (colored)

Fix for a bug in the change that walks the scoreboard backwards from
the tail (in tcp_sack_option()). The bug was caused by incorrect
accounting of the retransmitted bytes in the sackhint.

Reported by:    Kris Kennaway.
Submitted by:   Noritoshi Demizu.

mohan


--- Randy Bush <randy_at_psg.com> wrote:

> kernel: tcp_sack_output: Computed sack_bytes_retransmitted (1460) not the same as cached value
> (2920)
> kernel: tcp_sack_output: Computed sack_bytes_retransmitted (2920) not the same as cached value
> (4380)
> kernel: tcp_sack_output: Computed sack_bytes_retransmitted (1460) not the same as cached value
> (2920)
> kernel: tcp_sack_output: Computed sack_bytes_retransmitted (1460) not the same as cached value
> (2920)
> 
> FreeBSD x 6.0-CURRENT FreeBSD 6.0-CURRENT #9: Sun Jun  5 19:36:54 GMT 2005    
> root:/usr/obj/usr/src/sys/G  i386
> 
> this is first time i have seen this.
> 
> randy
> 
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>