Date: Wed, 15 Jun 2022 10:05:35 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 264257] [tcp] Panic: Fatal trap 12: page fault while in kernel mode (if_io_tqg_4) - m_copydata ... at /usr/src/sys/kern/uipc_mbuf.c:659 Message-ID: <bug-264257-7501-8QPDr3Np9X@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264257-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-264257-7501@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=3D264257 --- Comment #60 from Richard Scheffenegger <rscheff@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=3D0 = would not exhibit a panic. The patches added here really are to gather more information - and delibera= tely 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). --=20 You are receiving this mail because: You are the assignee for the bug. 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-264257-7501-8QPDr3Np9X>