From nobody Sun Nov 19 20:38:51 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 4SYMtN0dWfz51JV5 for ; Sun, 19 Nov 2023 20:38:52 +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 4SYMtM6jqXz3DKZ for ; Sun, 19 Nov 2023 20:38:51 +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=1700426331; 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=GkGq2oFvuuU3jnVsNbhUujPd7X55StIi9kMbr2bAwFk=; b=M77E9SsvQDHah2PJS6iW0AFeEL/zZC5PlhhXYDTtLGb1yeYf0Eb/3hhPF1+QSiItMtXy5q piAOiTTX3zXQxlmWlpNzDZsvrSyCgoSmSx/KmkkS3C9s6sIwXIjNMFXSvGqL3sCERE694o aWTqxPldATgAtqZ7ohph3vlOya0doHSQwI9UupMnesivYSa3ycm/mfgqU6xvIxPan3baM9 fF9jY9wbKH++WhSbcONhNrZEJ0zP953oc68MTtuORMUKpzscsI5UbGmWjRnRGwTvfPYzOs vpOgYkbCm2H1pNz0ZYzYtse1ALYlgRjyeLe/BcsvsrsEMKG1ZZpIHiPjH9nX2w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1700426331; a=rsa-sha256; cv=none; b=UTLA8rjAyD0Y2iCsteoZbOhJO/UOc83gWyzRUif9T3yB8pxqa9En2qOovZZ55S2N/BJYsg W7Qcn3Q23ULWNI2oqV273e9aB2wCI8mF83A8xNUNLnORHHo9GlsvkcxUt5ra0pE86h4blQ jwaP33MMPuovJNIx7oQUGptmJivJluDtEmUB0kPa5/93pdJ6l+e7UAZP1Us/qH0AQId1Yc cTOH7Y++Bh7k7IELhQB2SYeqfHcaE4Yy4BISFOMifMz71a+CDtuWDFSImLGF9Fg+aDAH3l Mtlff0R0BkWavAcF6v1xOhXKjwvJV3OonJTsR09A0JXFcfwNdhvV75+AdGJGcQ== 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 4SYMtM5mhjz8r5 for ; Sun, 19 Nov 2023 20:38:51 +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 3AJKcpll097290 for ; Sun, 19 Nov 2023 20:38:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3AJKcpXm097289 for bugs@FreeBSD.org; Sun, 19 Nov 2023 20:38:51 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 275169] Panic: rw_rlock: wlock already held for tcpinp @ /usr/src/sys/netinet/in_pcb.c:2529 Date: Sun, 19 Nov 2023 20:38:51 +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.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: i.dani@outlook.com X-Bugzilla-Status: New 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 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275169 --- Comment #9 from Dani I. --- (In reply to Michael Tuexen from comment #5) Thanks for triaging! As kp@ isn't responsible for ipfw - do you know who co= uld maybe help there? Thanks! (In reply to Gleb Smirnoff from comment #8) For us it's currently the "worst" option to upgrade to 14.0, as we're alrea= dy having issues with 13.2 and we didn't make very good experiences with early RELENG-Releases in the past. As we didn't have these issues with 12.4, we'd prefer to debug this further with 13.2 and would also be able to revert commits, test patches and try de= bug builds. We also saw that there weren't that much changes for ipfw between 1= 2.4 and 13.2 - so maybe the changes are somewhere else in the network stack. The question is, where to search and what could have an impact here. We'd really appreciate any help to narrow it down and find releated changes between 12.4 and 13.2 that might cause the issue.(In reply to Gleb Smirnoff from comment= #8) --=20 You are receiving this mail because: You are the assignee for the bug.=