Date: Sun, 19 Nov 2023 20:38:51 +0000 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 Message-ID: <bug-275169-227-i6hPBelcGI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275169-227@https.bugs.freebsd.org/bugzilla/> References: <bug-275169-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D275169 --- Comment #9 from Dani I. <i.dani@outlook.com> --- (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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275169-227-i6hPBelcGI>