> On 23. Jan 2019, at 21:41, Freddie Cash <fjwc...@gmail.com> wrote:
> 
> On Wed, Jan 23, 2019 at 12:34 PM Scheffenegger, Richard <
> richard.scheffeneg...@netapp.com> wrote:
> 
>> Hi,
>> 
>> we encounted an issue with the BSD11 cubic implementation during testing,
>> when dealing with app-stalled and app-limited traffic patterns.
>> 
>> The gist is, that at least in the after_idle cong_func for cubic, the
>> states for ssthresh and cubic epoch time are not reset, leading to
>> excessive cwnd values (overflows even) and self-inflicted drops due to
>> dramatic burst transmissions.
>> 
>> Bug Report, or Patch directly to Phabricator (when it is fully qualified)?
>> 
> 
> Search the freebsd-stable mailing list archives for the thread with subject
> line:
> 
> HEADS UP: TCP CUBIC Broken on 12.0-RELEASE/STABLE
> 
> https://lists.freebsd.org/pipermail/freebsd-stable/2018-December/090255.html
> 
> An Errata Notice should be going out sometime this month-ish.
Aren't you referring to:
https://www.freebsd.org/security/advisories/FreeBSD-EN-19:01.cc_cubic.asc

Best regards
Michael
> 
> -- 
> Freddie Cash
> fjwc...@gmail.com
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Reply via email to