From owner-freebsd-current Sun Mar 25 22:36:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id E430037B71B for ; Sun, 25 Mar 2001 22:36:38 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2Q6ab357215; Mon, 26 Mar 2001 08:36:37 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: si_drv1 used already? In-Reply-To: Your message of "Sun, 25 Mar 2001 22:20:59 -0800." <3ABEDFCB.4FDD0B47@elischer.org> Date: Mon, 26 Mar 2001 08:36:37 +0200 Message-ID: <57213.985588597@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3ABEDFCB.4FDD0B47@elischer.org>, Julian Elischer writes: >Poul-Henning Kamp wrote: >> >> In message <3ABEC9C7.F6C759CA@elischer.org>, Julian Elischer writes: >> > >> >The vmware vmmon driver used to use si_drv1 but suddenly it appears to >> >have already been used (at least it is no-longer non-zero). >> >It would fail to open because it checks it before using it during open. >> >Changing the driver to use si_drv2 fixes the problem. >> > >> >Since drv1 is defined as 'for the use of the driver' >> >I am not sure that it is wrong for the driver to use it. >> >In fact many other drivers do use it without testing it. >> > >> >I see it's used in freedev() and make_dev_alias(). >> >Is it safe for the driver to use it even if it is non-zero? >> >> I think you need to give me a bit more details before I an answer >> meaningfully... >> >> Are you sure that the value is not from previous use by vmmon ? > >no I am not sure.. I will test further. >the sequence: >1/ failed to open >2/ unload module Make sure vmmon calles destroy_dev() on all dev_t's created with make_dev() or make_dev_alias() when unloaded. This process is not automatic, and I am not sure we can safely make it automatic. We may be able to make it easier though. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | 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