Date: Mon, 20 Nov 2023 22:02:37 +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-a32TvhE0Me@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 #15 from Dani I. <i.dani@outlook.com> --- (In reply to Mark Johnston from comment #11) (In reply to Gleb Smirnoff from comment #14) Hey guys, thanks already for assisting and helping! That is really very much appreciated! Please just get back to us if we can help in any way! I'm not sure what time range you mean when you say "I assumed that ether_ip= fw & uid/gid rules problem has been there since very beginning and is well known, maybe even documented. :)", but as mentioned in the initial bug report, we didn't not have this issue at all with FreeBSD 12.4. The same hardware and = ipfw rules (with uid matching) worked like a charm and without any problem. So t= here must have been some changes between 12.4 and 13.2 which causes this "new" behavior. --=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-a32TvhE0Me>