From nobody Tue Jan 10 06:29:28 2023 X-Original-To: bugs@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 4Nrgrm5Gb0z2qpyC for ; Tue, 10 Jan 2023 06:29:28 +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 4Nrgrm4BJmz46K7 for ; Tue, 10 Jan 2023 06:29:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1673332168; 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=a2aSE439uvFMgWoqe78VVtatdz/w0hNKHb/xRsNf1pM=; b=UA6URpZOvG9DYvazfBQMnorqT7eZgIsN/vR72f2v9JI811OsYRcyQco1HDMrDxldgUDeXF VeJoTmepIilzzNFmKz2yHzS8dBA0f+oiKVRFfSgMyMmEJbEFp3aCf3mOoqdgAZp+O3idbT Vk/cwCVdLiptiu+6FYj4KP2uxa83D2tEKlb+/OKpVml7B6+I6sfRZn0GHc8FHKESAQsKrz 7XlolZSmvghJd9kO3nNxzQe2GsBtUN3PMKPnsas34yrzcwAUdwggYgCz+FFbOfs5Bwg+1S ln6kZWsEJ1ZnB1SRhyI0vhg5yq1jiR1gqmoQBsXyQq8HfuCy9eTtEuykYPjd7Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1673332168; a=rsa-sha256; cv=none; b=k77mJ9dRJaI/DieBrvzpNWUKL+h7QjYtbjivS71WLetBzoUkjjPonUCGpRC188Y5oXI/da ZxgDumF39DlfITZD8vYa93ftpNRr/Y9IS4VjYALObUsiNb4KyHCV0KXYrCui/LkXl/+pMu 7mPwcvTpR3vkfeQ1qunGtivOo4PUninaKCfDq+N5+7vvEnSady17BGXNLAtS0YiQgwoPb+ w+fKbbF7rwQGEkneNwFHhC7sGkaRaBqvT+gLKw42aiKUWQLU/hJCtVKvrRZxYppOyw2Qwn tbe0EfHQh3MdYgD0DKSfjCugKknlURY59ds/+kH0Sg7Njz3lZphx/bXc/61duw== 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 4Nrgrm37yGzyXW for ; Tue, 10 Jan 2023 06:29:28 +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 30A6TSHC068131 for ; Tue, 10 Jan 2023 06:29:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 30A6TSL7068130 for bugs@FreeBSD.org; Tue, 10 Jan 2023 06:29:28 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: bugs@FreeBSD.org Subject: [Bug 268246] crash and panic using pfsync on 13.1-RELEASE Date: Tue, 10 Jan 2023 06:29:28 +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: 13.1-RELEASE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kp@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@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: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268246 --- Comment #16 from Kristof Provost --- So my current guess is that there's something wrong with the mbuf that the pfsync code produced. Presumably that it's not as long as we're expecting i= t to be, which causes the fragmentation code to run off the end of the mbuf chain and blow up. It's not clear to me how that'd happen, but it would be useful to experiment with the pfsync interface MTU. Try setting it to less than 4k (maybe back d= own to 1500) and see if the panic goes away. m_get2() allocates external storage for > MCLBYTES (4k) allocations, but th= at should still just work, at least according to my reading of the relevant co= de. It may be that I'm missing something. The above experiment should provide a nice data point for that. --=20 You are receiving this mail because: You are the assignee for the bug.=