From owner-freebsd-current@FreeBSD.ORG Tue Jun 29 03:41:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 680) id D731416A4CF; Tue, 29 Jun 2004 03:41:34 +0000 (GMT) Date: Tue, 29 Jun 2004 03:41:34 +0000 From: Darren Reed To: Max Laier Message-ID: <20040629034134.GA39840@hub.freebsd.org> References: <20040624192630.GA739@gothmog.gr> <200406260112.53490.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406260112.53490.max@love2party.net> User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Tue, 29 Jun 2004 12:12:27 +0000 cc: Giorgos Keramidas cc: freebsd-current@freebsd.org Subject: Re: FIX: today's ipfilter "mutex not locked" panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2004 03:41:35 -0000 On Sat, Jun 26, 2004 at 01:12:44AM +0200, Max Laier wrote: > On Thursday 24 June 2004 21:26, Giorgos Keramidas wrote: > > FWIW, > > > > I've locally fixed the panics that some people mentioned today for > > ipfilter with the following minor diff. Now I can enable ipfilter > > at boot time and still boot without panics. [...] Sorry for the delay, have been "busy"... The patch provided has been reviewed (looks good :) and committed. Darren