I have pulled down the reproducers.. one thing to note is they are all rack (though it could be that the problems are also in BBR). And of course FreeBSD is behind NF in rack at least.
I need to work on getting things updated.. one thing Michael, both Rack and BBR in NF have lost the OOB handling. Please do not commit any more changes to Rack .. since that work has already been done. R > On Apr 26, 2020, at 7:28 AM, Randall Stewart <[email protected]> wrote: > > This is actually the first I have heard of these bugs⦠> > I will have look at them Mark. > > R > >> On Apr 24, 2020, at 10:23 AM, Mark Johnston <[email protected]> wrote: >> >> On Fri, Apr 24, 2020 at 03:15:08PM +0100, Tom Jones wrote: >>> [email protected] >>> Bcc: >>> Subject: Re: How to enable tcp bbr in FreeBSD??? >>> Reply-To: >>> In-Reply-To: <[email protected]> >>> >>> >>> ... snip ... >>>> >>>> Maybe it is not ready for prime time, i do not know why it is not in the >>>> default build. >>>> Maybe ask the committer. >>>> >>> >>> I have added rrs@ in cc and the freebsd-transport list. >>> >>> Does anyone know if there are plans to enable alternate TCP stacks in >>> generic? >>> >>> Is there a stability point we need to hit first? >> >> There are a couple of open bugs found by syzkaller (complete with >> reproducers) that appeared when I enabled the alternate TCP stacks: >> >> https://syzkaller.appspot.com/bug?id=986b4cecd84439df9794bda1a45d9cf0f50356fe >> https://syzkaller.appspot.com/bug?id=048f650e99696f881872a285cef0e3b9bd4f4e25 >> >> I'd expect these to be fixed before providing the alternate stacks in >> GENERIC. >> _______________________________________________ >> [email protected] mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-transport >> To unsubscribe, send any mail to "[email protected]" > > ------ > Randall Stewart > [email protected] > > > ------ Randall Stewart [email protected] _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-transport To unsubscribe, send any mail to "[email protected]"
