https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264257
--- Comment #60 from Richard Scheffenegger <rsch...@freebsd.org> --- (In reply to Christos Chatzaras from comment #57) Sorry for being unclear: A plain (unpatched) 13.1-RELEASE kernel with net.inet.tcp.rfc6675_pipe=0 would not exhibit a panic. The patches added here really are to gather more information - and deliberately panic (when built with INVARIANTS) or retroactively adjust the incorrect TCP state. Stable operation in a production environment would only need the standard kernel, and it's safe to use SACK as long as rfc6675_pipe is not enabled. (The root cause - apparent double-accounting for FIN bits, and possibly even sending FIN bits at two different, final sequence numbers - would still be present, but not cause a crash). -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
