Date: Sun, 14 May 2000 21:59:16 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Mike Smith <msmith@FreeBSD.ORG> Cc: Nick Hibma <n_hibma@calcaphon.com>, Peter Edwards <peter.edwards@openet-telecom.com>, FreeBSD CURRENT Mailing List <current@FreeBSD.ORG>, wc.bulte@chello.nl, Maxim Sobolev <sobomax@altavista.net> Subject: Re: vn.ko load/unload/mount = panic Message-ID: <1385.958334356@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 14 May 2000 12:53:32 PDT." <200005141953.MAA09495@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200005141953.MAA09495@mass.cdrom.com>, Mike Smith writes: >> In message <Pine.BSF.4.20.0005141328380.78621-100000@localhost>, 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1385.958334356>