Date: Sun, 28 Sep 2003 22:45:38 +0100 From: Bruce M Simpson <bms@spc.org> To: Poul-Henning Kamp <phk@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/net if.c src/sys/dev/nmdm nmdm.c src/sys/dev/usb ugen.c uhid.c ulpt.c ums.c uscanner.c src/sys/netgraph/bluetooth/drivers/ubt ng_ubt.c src/sys/netgraph/bluetooth/drivers/ubtbcmfw ubtbcmfw.c Message-ID: <20030928214538.GD17996@saboteur.dek.spc.org> In-Reply-To: <200309282048.h8SKmD5d088918@repoman.freebsd.org> References: <200309282048.h8SKmD5d088918@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 28, 2003 at 01:48:13PM -0700, Poul-Henning Kamp wrote: > Log: > I don't know from where the notion that device driver should or > even could call VOP_REVOKE() on vnodes associated with its dev_t's > has originated, but it stops right here. > > If there are things people belive destroy_dev() needs to learn how to > do, please tell me about it, preferably with a reproducible test case. I have some drivers in my local tree which do this, to prevent any further use of the device when removal is detected. What alternative/workaround do you offer to achieve this functionality in the light of the change you are making? BMS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030928214538.GD17996>