From owner-freebsd-scsi@FreeBSD.ORG  Sun Apr  4 16:30:35 2010
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C16BA1065674
	for <freebsd-scsi@freebsd.org>; Sun,  4 Apr 2010 16:30:35 +0000 (UTC)
	(envelope-from mj@feral.com)
Received: from ns1.feral.com (ns1.feral.com [192.67.166.1])
	by mx1.freebsd.org (Postfix) with ESMTP id 8476C8FC16
	for <freebsd-scsi@freebsd.org>; Sun,  4 Apr 2010 16:30:35 +0000 (UTC)
Received: from [192.168.0.102] (m206-63.dsl.tsoft.com [198.144.206.63])
	by ns1.feral.com (8.14.3/8.14.3) with ESMTP id o34GUYtA093586
	for <freebsd-scsi@freebsd.org>; Sun, 4 Apr 2010 09:30:35 -0700 (PDT)
	(envelope-from mj@feral.com)
Message-ID: <4BB8BEB4.70606@feral.com>
Date: Sun, 04 Apr 2010 09:30:44 -0700
From: Matthew Jacob <mj@feral.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: freebsd-scsi@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.2.3
	(ns1.feral.com [192.67.166.1]);
	Sun, 04 Apr 2010 09:30:35 -0700 (PDT)
Subject: cam_periph_find
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Apr 2010 16:30:35 -0000

There is currently nothing that keeps a periph from disappearing between 
the time you find it with cam_periph_find and the try to 'acquire' it 
later (if you indeed do so).

What do people feel about changing the semantic of cam_periph_find to up 
the refcount (requiring the caller to release or release_locked)?