Date: Fri, 05 Mar 2021 17:35:20 +0000 From: bugzilla-noreply@freebsd.org To: transport@FreeBSD.org Subject: [Bug 253848] [tcp] panic: sackhint bytes rtx >= 0 Message-ID: <bug-253848-38102-FdWs0PQfML@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-253848-38102@https.bugs.freebsd.org/bugzilla/> References: <bug-253848-38102@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253848 --- Comment #6 from Richard Scheffenegger <rscheff@freebsd.org> --- It turned out that only under a specific set of circumstances - RTO during a SACK loss recovery, while the client had not yet fully reported back all SA= CK blocks - a unnecessary initialization of sack_bytes_rexmit caused this pani= c.=20 In mundane environments this was virtually not reproduceable, and even in exposed environments, tcp sessions apparently need to suffer from sudden RTT jumps / path changes to elicit the panic. Thanks to rrs@ and gallatin@ for helping by providing crucial timing and pa= cket trace/tcp state information around a few occurances. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253848-38102-FdWs0PQfML>