From owner-freebsd-current Sun May 14 12:59:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D888137B99D; Sun, 14 May 2000 12:59:18 -0700 (PDT) (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 VAA01387; Sun, 14 May 2000 21:59:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith 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 12:53:32 PDT." <200005141953.MAA09495@mass.cdrom.com> Date: Sun, 14 May 2000 21:59:16 +0200 Message-ID: <1385.958334356@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200005141953.MAA09495@mass.cdrom.com>, Mike Smith writes: >> 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). disk_destroy is different from destroy_dev, and I'll get to it real soon. >Also, while you still can, that should be dev_destroy(). No, because the corresponding is called make_dev(). -- 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