From owner-freebsd-current Sun May 14 7:27:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from bogon.freebsd.dk (bogon.freebsd.dk [212.242.40.178]) by hub.freebsd.org (Postfix) with ESMTP id C76D137B743 for ; Sun, 14 May 2000 07:27:04 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk ([212.242.127.222]) by bogon.freebsd.dk (8.9.3/8.9.3) with ESMTP id QAA20501; Sun, 14 May 2000 16:26:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id QAA02086; Sun, 14 May 2000 16:26:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nick Hibma Cc: 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 13:33:14 BST." Date: Sun, 14 May 2000 16:26:42 +0200 Message-ID: <2084.958314402@critter.freebsd.dk> From: Poul-Henning Kamp 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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message