From owner-freebsd-current@FreeBSD.ORG Tue Feb 27 19:53:58 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 977E816A5D0 for ; Tue, 27 Feb 2007 19:53:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 48AF313C4AA for ; Tue, 27 Feb 2007 19:53:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l1RJrjc7052936; Tue, 27 Feb 2007 14:53:47 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Danny Braniss Date: Tue, 27 Feb 2007 13:03:43 -0500 User-Agent: KMail/1.9.1 References: <200702261653.48794.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702271303.44239.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 27 Feb 2007 14:53:47 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2665/Tue Feb 27 11:26:03 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@freebsd.org Subject: Re: problems porting iSCSI to current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 19:53:58 -0000 On Tuesday 27 February 2007 05:26, Danny Braniss wrote: > > On Monday 19 February 2007 04:53, Danny Braniss wrote: > > > Hi all, > > > im getting stuck in destroy_dev(...) because > > > si_threadcount is not zero, (actually 1 before the call), > > > all this in sys/kern_conf.c. > > > what magic am I doing wrong? > > > > Don't call destroy_dev() in your close routine. > > > and how will the device created by make_dev get destroyed? > merlin to the rescue ... I agree it's not clear, and I'm not using cloning in ipmi(4) until it makes sense. -- John Baldwin