From owner-freebsd-net@freebsd.org Tue Jan 28 10:50:41 2020 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 877EF1FE20A for ; Tue, 28 Jan 2020 10:50:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 486Ngj32w3z3G1Z for ; Tue, 28 Jan 2020 10:50:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 66A6C1FE206; Tue, 28 Jan 2020 10:50:41 +0000 (UTC) Delivered-To: net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 666371FE204 for ; Tue, 28 Jan 2020 10:50:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 486Ngj26Nhz3G1W for ; Tue, 28 Jan 2020 10:50:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 29C2921B95 for ; Tue, 28 Jan 2020 10:50:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 00SAofMv074654 for ; Tue, 28 Jan 2020 10:50:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 00SAofD9074653 for net@FreeBSD.org; Tue, 28 Jan 2020 10:50:41 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 243392] if_vmx(4): Input buffer corruption Date: Tue, 28 Jan 2020 10:50:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: mfc-stable12? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jan 2020 10:50:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243392 --- Comment #7 from Andriy Gapon --- When I run tcpdump on the other end, there is no effect on the speed. There are some potentially interesting snippets in the capture. Here is one where 10.25.200.199 is the vmx side and 10.180.0.51 is the other host that sends data to the vmx host: 115 02:16:28.787281 IP 10.180.0.51.17739 > 10.25.200.199.22: Flags [.], = seq 81774:83160, ack 1, win 1026, options [nop,nop,TS val 3595053000 ecr 1184721692], length 1386 116 02:16:28.787284 IP 10.180.0.51.17739 > 10.25.200.199.22: Flags [.], = seq 83160:84546, ack 1, win 1026, options [nop,nop,TS val 3595053000 ecr 1184721692], length 1386 117 02:16:28.787304 IP 10.180.0.51.17739 > 10.25.200.199.22: Flags [.], = seq 84546:85932, ack 1, win 1026, options [nop,nop,TS val 3595053000 ecr 1184721692], length 1386 118 02:16:28.787307 IP 10.180.0.51.17739 > 10.25.200.199.22: Flags [.], = seq 85932:87318, ack 1, win 1026, options [nop,nop,TS val 3595053000 ecr 1184721692], length 1386 119 02:16:28.883545 IP 10.25.200.199.22 > 10.180.0.51.17739: Flags [.], = ack 83160, win 2192, options [nop,nop,TS val 1184721792 ecr 3595053000], length= 0 120 02:16:28.883576 IP 10.180.0.51.17739 > 10.25.200.199.22: Flags [.], = seq 87318:88704, ack 1, win 1026, options [nop,nop,TS val 3595053097 ecr 1184721792], length 1386 121 02:16:28.887035 IP 10.25.200.199.22 > 10.180.0.51.17739: Flags [.], = ack 83160, win 2192, options [nop,nop,TS val 1184721792 ecr 3595053000,nop,nop,= sack 1 {87318:88704}], length 0 122 02:16:29.336381 IP 10.180.0.51.17739 > 10.25.200.199.22: Flags [.], = seq 83160:84546, ack 1, win 1026, options [nop,nop,TS val 3595053549 ecr 1184721792], length 1386 My reading of the above. Packets 115-118: data packets Packet 119: ack for packet 115 Packet 120: another data packet Packet 121: appears to be exact duplicate of the packet 119 (ack) Packet 122: looks like a retransmission of packet 116 after a noticeable de= lay (0.44s) Well, on another look, packets 119 and 121 are not exactly the same. 121 has this "sack 1 {87318:88704}" that 119 does not have. And it seems like packet 121 is what "confuses" the sending side as the pau= se and retransmission. Not a TCP expert, so don't know if anything is wrong here. --=20 You are receiving this mail because: You are the assignee for the bug.=