Date: Sat, 25 Sep 2004 00:55:55 +0200 From: Max Laier <max@love2party.net> To: "Christian S.J. Peron" <csjp@freebsd.org> Cc: freebsd-pf@freebsd.org Subject: Re: fixes for ipfw and pf lock ordering issues Message-ID: <200409250056.10275.max@love2party.net> In-Reply-To: <20040924223754.GA86799@freefall.freebsd.org> References: <20040924223754.GA86799@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart4033428.rfQkKE7BF2 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 25 September 2004 00:37, Christian S.J. Peron wrote: > Good day folks, we need some beta testers > > Currently, those who utilize ucred based firewalling, i.e. firewall > rules which match based on UID, GID or JAIL ID are subject to lock order > problems which often results in the system hard locking. (when giant > is not present ... debug.mpsafenet=3D1). > > This problem affects all FreeBSD firewalls which implement ucred based > matching, namely ipfw and pf. The lock order problem exists due to a > layering violation which occurs when the IP stack attempts to acquire > locks within lower level stacks such as UDP and TCP. =46or the record [just realized that we forgot]: Talking about LOR id 14-17= ... =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart4033428.rfQkKE7BF2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBVKYKXyyEoT62BG0RAn4eAJ46af5V5qDZOC5y1Nkf51CLfDDH7QCffFFa KQ2b9SmNIRWsgpa8pz4KveU= =1xo3 -----END PGP SIGNATURE----- --nextPart4033428.rfQkKE7BF2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409250056.10275.max>