From owner-freebsd-arch@FreeBSD.ORG Sat Mar 15 19:48:07 2008 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8105106564A for ; Sat, 15 Mar 2008 19:48:07 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 8812B8FC1A for ; Sat, 15 Mar 2008 19:48:07 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.64.3]) by phk.freebsd.dk (Postfix) with ESMTP id 7AFBF17104; Sat, 15 Mar 2008 19:48:05 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m2FJm4U5006719; Sat, 15 Mar 2008 19:48:04 GMT (envelope-from phk@critter.freebsd.dk) To: Ed Schouten From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 15 Mar 2008 13:40:08 +0100." <20080315124008.GF80576@hoeg.nl> Date: Sat, 15 Mar 2008 19:48:04 +0000 Message-ID: <6718.1205610484@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: FreeBSD Arch Subject: Re: vgone() calling VOP_CLOSE() -> blocked threads? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Mar 2008 19:48:07 -0000 >To be honest, I'm not completely sure how to solve this issue, though I >know it should at least do something similar to this: > >- The device driver should have a seperate routine (d_revoke) to wake > up any blocked threads, to make sure they leave the device driver > properly. It's already there, it's called d_purge(). -- 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.