Date: Tue, 21 Jun 2022 08:23:52 +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-WWdKzFAehM@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 #70 from Richard Scheffenegger <rscheff@freebsd.org> --- (In reply to Christos Chatzaras from comment #68) >From the provided core: snd_una: 2568161219 snd_nxt: 2568161624 snd_max: 2568161624 snd_fack: 2568161624 (!!) so_snd: 403 snd_una + so_snd: 2568161622 *tp->sackhint->nexthole {start =3D 2568161219, end =3D 2568161623, rxmit =3D 2568161622, ... This indicates, that the remote client SACKed the 2nd FIN bit (which appare= ntly was sent at sequence number 2568161624, not 2568161623 as expected). The SACK for this 2nd FIN created a SACK scoreboard hole, which included the sequence number of the 1st FIN bit - which does not exist in the socket sendbuffer. Thus when trying to retransmit this non-existing byte, the panic happens. --=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-WWdKzFAehM>