From nobody Mon Dec 18 22:32:08 2023 X-Original-To: transport@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SvF1j13r5z54C9N for ; Mon, 18 Dec 2023 22:32:09 +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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SvF1h5Zw9z3D3d for ; Mon, 18 Dec 2023 22:32:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1702938728; a=rsa-sha256; cv=none; b=nYIOY1lIjPuzdxBOIB1He7JQ532R8TQDPaDmPCxxyN14AvhYdfriWIemtBpxaR1zWByqWn 18AUADdu8EuOzNAaOO4S2qdUiIPaKsDFnFOcxQ1WcTJGcKe0AWnGonPjtnRUY0N0O4EsbW BrJo+ecsxbMYnbmYc1ooxZDbOXVvvxkTv3rxoBeTmLi/xfWajwncEhARFxbVM4W775Y6pl WAreJ4hePt2VphXpcwV0ka15nwg5RwRdgLlxXOaq2qfHX2nsKhVBd8YLXqou48M7Qe8JEE AAdjwtJpVL1dLHq6/HnLki2sxGxTbowwANd1rD5rAeZ+ZAjix5K+MmPM/rNO1A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1702938728; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=LCBo4zfuyZyeBV6rAefUutBAaQ7nGnwQ2msh43AuqUs=; b=UZAc2r3pLyfdiWBxIKy+uf6XEhKGMUSuPRriO24xP966opDpLPKU/94HOH+TOjoGw5luXi 7nE+766yvrgpGdG0DTHusTNYp9rel2WJ6+xbccvC8BQJh8h1x5G0Pg+YHjrAO0XkYSq1Qq WToQYOvRjxqbemymhmCMLrA5b8s8kII5BR5XByHKS90cVEC5JztjvbWRi7GIJQ+ahJqUNI zXQQ8qBGnvGHh6Ti+GGAw1POfqauMl6HFci+tL3SRAVkmVzmm5mmUv8r4wNtwL/Z0SDYVc /dc5n5I9/Sks22ha217mTpnvpN2KaGxgfYjC90x3H7ELUz3AEYw8VEa68EJt2g== 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) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4SvF1h3wGszfP7 for ; Mon, 18 Dec 2023 22:32:08 +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 3BIMW8Hh087859 for ; Mon, 18 Dec 2023 22:32:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3BIMW89b087858 for transport@FreeBSD.org; Mon, 18 Dec 2023 22:32:08 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: transport@FreeBSD.org Subject: [Bug 275798] panic: sackhint bytes rtx >= 0 Date: Mon, 18 Dec 2023 22:32:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: rscheff@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: rscheff@freebsd.org X-Bugzilla-Flags: 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 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-transport List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-transport@freebsd.org X-BeenThere: freebsd-transport@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275798 --- Comment #10 from Richard Scheffenegger --- It appears that the issue may have to do with some LRO going on as well on = the receiver side - which doesn't ACK each individual packet, but typically 2 consecutive one, even while the receiver knows loss/reordering is on-going.= At that stage the receiver normally would ACK every packet received... The ultimate issue appears to happen after a RTO timeout, when the last outstanding (2-packet) hole is filled, and the cumulative ACK covering it a= ll also contains a DSACK block at the beginning of the former hole... Normally, such a DSACK block should be discareded and ignored during the SA= CK update process - not really sure why it's apparently processed erraneously, leading to the panic... --=20 You are receiving this mail because: You are on the CC list for the bug.=