From owner-freebsd-current Sun May 14 13: 5:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id 4115937B506 for ; Sun, 14 May 2000 13:05:41 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA09495; Sun, 14 May 2000 12:53:32 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005141953.MAA09495@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Poul-Henning Kamp Cc: Nick Hibma , Peter Edwards , FreeBSD CURRENT Mailing List , wc.bulte@chello.nl, Maxim Sobolev Subject: Re: vn.ko load/unload/mount = panic In-reply-to: Your message of "Sun, 14 May 2000 16:26:42 +0200." <2084.958314402@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 May 2000 12:53:32 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message , Nick Hibma wri > tes: > > > >Correct me if I am wrong, but I don't think you actually have to > >disassociate any dev_t's from the driver (by clearing the si_drv[12] > >fields) because we call destroy_dev and cdevsw_remove, so any later uses > >of dev_t's get an error because the device has gone away. > > destroy_dev will clear the necessary fields in a dev_t, cdevsw_remove > will not. Is it correct to assume that destroy_dev() still isn't working correctly? (disk_destroy certainly isn't). Also, while you still can, that should be dev_destroy(). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message