From owner-freebsd-current@FreeBSD.ORG Wed Aug 17 19:28:46 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A3C416A41F for ; Wed, 17 Aug 2005 19:28:46 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5715443D48 for ; Wed, 17 Aug 2005 19:28:45 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id j7HJSZue013721; Wed, 17 Aug 2005 22:28:39 +0300 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id j7HJYJSU002486; Wed, 17 Aug 2005 22:34:19 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id j7HJYCsp002485; Wed, 17 Aug 2005 22:34:12 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Wed, 17 Aug 2005 22:34:12 +0300 From: Giorgos Keramidas To: Brooks Davis Message-ID: <20050817193412.GA2446@flame.pc> References: <20050817141436.GB1143@unixpages.org> <20050817185447.GC16558@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050817185447.GC16558@odin.ac.hmc.edu> Cc: current@freebsd.org Subject: Re: Pending if_fwip.c patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 17 Aug 2005 19:28:46 -0000 On 2005-08-17 11:54, Brooks Davis wrote: > On Wed, Aug 17, 2005 at 04:14:36PM +0200, Christian Brueffer wrote: > > Hi, > > > > can someone commit the attached patch for if_fwip.c? It fixes a panic > > on attach and has been reviewed by dfr@. > > Done. Apparently there's aren't a lot of fwip users of current since I > broke that over a month ago. :( I stumbled upon the same panic last week too, but removed fwip from my kernel config and moved on because I had no time to find out what was wrong. It's good to see that this is fixed now :))) Thanks!