From owner-freebsd-current@FreeBSD.ORG Sat Aug 28 02:51:33 2004 Return-Path: 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 1621816A4CE for ; Sat, 28 Aug 2004 02:51:33 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8575443D1F for ; Sat, 28 Aug 2004 02:51:32 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i7S2jYlG020794; Fri, 27 Aug 2004 20:47:41 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 27 Aug 2004 20:45:34 -0600 (MDT) Message-Id: <20040827.204534.05064067.imp@bsdimp.com> To: doconnor@gsoft.com.au From: "M. Warner Losh" In-Reply-To: <200408271232.05202.doconnor@gsoft.com.au> References: <200408261211.41920.doconnor@gsoft.com.au> <20040826103813.GA523@gicco.homeip.net> <200408271232.05202.doconnor@gsoft.com.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: hampi@rootshell.be Subject: Re: unloading ums and usb 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: Sat, 28 Aug 2004 02:51:33 -0000 In message: <200408271232.05202.doconnor@gsoft.com.au> "Daniel O'Connor" writes: : -----BEGIN PGP SIGNED MESSAGE----- : Hash: SHA1 : : On Thu, 26 Aug 2004 20:08, Hanspeter Roth wrote: : > > USB is not really un-loadable at this stage although it is being worked : > > on. I am not sure how long it will take, or if it will get MFC'd : > > (although I expect it will). : > : > Well, but unload of USB succeeds if there is no client loaded. : > Anyway, it sounds this bug is solved in -current. : : Heh, at best this will leak memory, at worst it will crash if you reload it or : otherwise poke it.. I'd agree with the characterization "in current, we're making it incrementally suck a lot less than it did before and maybe, just maybe, the suckage factor will go away completely if we do it enough times." Warner