From owner-freebsd-ipfw@FreeBSD.ORG Fri Sep 24 22:57:06 2004 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58D8D16A4CE; Fri, 24 Sep 2004 22:57:06 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BD8243D5F; Fri, 24 Sep 2004 22:57:06 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CAyzx-0000ms-00; Sat, 25 Sep 2004 00:57:05 +0200 Received: from [217.83.1.154] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CAyzx-0002SW-00; Sat, 25 Sep 2004 00:57:05 +0200 From: Max Laier To: "Christian S.J. Peron" Date: Sat, 25 Sep 2004 00:55:55 +0200 User-Agent: KMail/1.7 References: <20040924223754.GA86799@freefall.freebsd.org> In-Reply-To: <20040924223754.GA86799@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4033428.rfQkKE7BF2"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200409250056.10275.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: bz@freebsd.org cc: hackers@freebsd.org cc: ipfw@freebsd.org cc: freebsd-pf@freebsd.org Subject: Re: fixes for ipfw and pf lock ordering issues X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2004 22:57:06 -0000 --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--