From owner-freebsd-net@freebsd.org Thu Feb 25 19:00:27 2021 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 3E67C56D278 for ; Thu, 25 Feb 2021 19:00:27 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4Dmhtz19rpz3GDJ for ; Thu, 25 Feb 2021 19:00:27 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id 284F156D1CF; Thu, 25 Feb 2021 19:00:27 +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 2815856D36D for ; Thu, 25 Feb 2021 19:00:27 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from relay12.mail.gandi.net (relay12.mail.gandi.net [217.70.178.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Dmhty5nvNz3GHN; Thu, 25 Feb 2021 19:00:26 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from [192.168.0.88] (unknown [195.64.148.76]) (Authenticated sender: andriy.gapon@uabsd.com) by relay12.mail.gandi.net (Postfix) with ESMTPSA id 77AD7200002; Thu, 25 Feb 2021 19:00:22 +0000 (UTC) Subject: Re: panic: sackhint bytes rtx >= 0 To: Michael Tuexen Cc: "Scheffenegger, Richard" , "net@FreeBSD.org" References: <960081ac-2839-a226-3142-5a4666eb54ad@FreeBSD.org> <8BB910F9-B828-49A2-8941-4F6C6419D8EA@freebsd.org> <58AED4F6-FBA4-46D5-98D4-DD31BD9A946B@freebsd.org> From: Andriy Gapon Message-ID: Date: Thu, 25 Feb 2021 21:00:21 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Firefox/78.0 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: <58AED4F6-FBA4-46D5-98D4-DD31BD9A946B@freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4Dmhty5nvNz3GHN X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2021 19:00:27 -0000 On 25/02/2021 20:20, Michael Tuexen wrote: >> On 25. Feb 2021, at 19:08, Andriy Gapon wrote: >> >> On 24/02/2021 00:40, Scheffenegger, Richard wrote: >>> Hi Andriy, >>> >>> I guess I am currently the person who has the most recent knowledge about that >>> part of the base stack… >>> >>> Do you happen to have more (preceding) information about this, or a way to >>> reproduce this? >> Unfortunately, no. It "just happened". >> There was no unusual activity at the time of the crash. >> At least, from a user / administrator perspective. > So you did not use specific TCP stacks or congestion control modules? Correct. The default stack and congestion control (if any). >>> Are you running any special stack (RACK, BBR) which may have switched back to >>> the base stack in the middle of a loss recovery (I suspected at one point that >>> this may cause issues, potentially)? >> I do not have any customizations to the network stack, everything at defaults. >> >>> Or was something done with the ipfw that may have temporarily impacted a tcp >>> session? >> I use pf as a firewall. I did not touch it at the time of the crash. > Does pf change the packets? Not sure. If only this rule: scrub in all fragment reassemble All others are just block and pass (no NAT even). -- Andriy Gapon