Date: Sun, 07 Dec 2003 20:13:42 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: ticso@cicely.de Cc: freebsd-current@freebsd.org Subject: Re: major number leak with modules? Message-ID: <26334.1070824422@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 07 Dec 2003 18:40:00 %2B0100." <20031207173959.GE42518@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20031207173959.GE42518@cicely12.cicely.de>, Bernd Walter writes: >The situation was the following during driver development. >It's an USB driver and kldload'ed. >A plugged in device got major 247 for the nodes it created. >On unplugging the nodes were destroyed. >kldunloading the driver and kldloading the next revision created >nodes with major 246 for new devices. > >Do we have a leak with major numbers or is the old major number free >after last destroy_dev and assigning algorithm just took the next. Yes, repeatedly loading/unloading will leak majors. I have some ref-counting code to solve this problem. Warners axe-swinging in the old ISA drivers made it easier, but some necessary but uncommitted patches to the sound code from cg@ are still at road-block. -- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26334.1070824422>