From owner-freebsd-current@FreeBSD.ORG Thu Nov 23 21:07:10 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6808F16A415; Thu, 23 Nov 2006 21:07:10 +0000 (UTC) (envelope-from fbsd-current@mawer.org) Received: from customer-domains.icp-qv1-irony13.iinet.net.au (customer-domains.icp-qv1-irony13.iinet.net.au [203.59.1.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66EBC43D81; Thu, 23 Nov 2006 21:06:21 +0000 (GMT) (envelope-from fbsd-current@mawer.org) Received: from 203-206-173-235.perm.iinet.net.au (HELO [127.0.0.1]) ([203.206.173.235]) by customer-domains.icp-qv1-irony13.iinet.net.au with ESMTP; 24 Nov 2006 05:06:56 +0800 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAKKbZUXLzq3r/2dsb2JhbAANiFQ X-IronPort-AV: i="4.09,453,1157299200"; d="scan'208"; a="31032834:sNHT20463282" Message-ID: <45660D01.9000102@mawer.org> Date: Fri, 24 Nov 2006 08:05:05 +1100 From: Antony Mawer User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Robert Watson References: <20061123114254.GO1841@deviant.kiev.zoral.com.ua> <20061123115046.S50054@fledge.watson.org> In-Reply-To: <20061123115046.S50054@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , current@freebsd.org Subject: Re: if_ef rotten 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: Thu, 23 Nov 2006 21:07:10 -0000 On 23/11/2006 10:55 PM, Robert Watson wrote: > > On Thu, 23 Nov 2006, Kostik Belousov wrote: > >> When trying to kldload if_ef (on yesterday CURRENT/amd64, with WITNESS >> and almost all debugging enabled), I got a lot of "malloc(M_WAITOK) of >> "XXX", forcing M_NOWAIT with the following non-sleepable locks held: >> ... ifnet ..." >> >> Is it rotten ? (No, I do not use it, just noted it when doing some >> other testing work). > > There are three general classes of problems with if_ef: ... If you are looking for any testers of if_ef-related work, we use it quite heavily (with nwfs and IPX), although my -CURRENT test machine is currently in pieces, so I haven't done any testing on -CURRENT just at the moment! If you need any additional information from a in-use environment, patches to be tested, etc, I'll volunteer... --Antony