From owner-cvs-all@FreeBSD.ORG Sun Sep 28 16:24:48 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF38116A4B3; Sun, 28 Sep 2003 16:24:48 -0700 (PDT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 454C844011; Sun, 28 Sep 2003 16:24:47 -0700 (PDT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 7C33B65452; Mon, 29 Sep 2003 00:24:45 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 41483-04-3; Mon, 29 Sep 2003 00:24:45 +0100 (BST) Received: from saboteur.dek.spc.org (lardystuffer.demon.co.uk [212.228.40.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id AC16F65449; Mon, 29 Sep 2003 00:24:42 +0100 (BST) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id E128BBC; Sun, 28 Sep 2003 22:45:38 +0100 (BST) Date: Sun, 28 Sep 2003 22:45:38 +0100 From: Bruce M Simpson To: Poul-Henning Kamp Message-ID: <20030928214538.GD17996@saboteur.dek.spc.org> Mail-Followup-To: Poul-Henning Kamp , src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org References: <200309282048.h8SKmD5d088918@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200309282048.h8SKmD5d088918@repoman.freebsd.org> cc: cvs-src@FreeBSD.org cc: src-committers@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 X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Sep 2003 23:24:48 -0000 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