From owner-freebsd-scsi Thu Aug 22 14: 9:40 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2413337B400; Thu, 22 Aug 2002 14:09:37 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 107C543E6A; Thu, 22 Aug 2002 14:09:36 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.5/8.12.5) with ESMTP id g7ML9VKD010941; Thu, 22 Aug 2002 15:09:31 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.5/8.12.5/Submit) id g7ML9VeQ010940; Thu, 22 Aug 2002 15:09:31 -0600 (MDT) (envelope-from ken) Date: Thu, 22 Aug 2002 15:09:31 -0600 From: "Kenneth D. Merry" To: Johan Karlsson Cc: nsayer@quack.kfu.com, freebsd-gnats-submit@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, freebsd-standards@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: kern/15608: acd0 / cd0 give inconsistent errors on empty tray open() Message-ID: <20020822150931.A10866@panzer.kdm.org> References: <200208221942.g7MJgMpY037865@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200208221942.g7MJgMpY037865@freefall.freebsd.org>; from johan@FreeBSD.ORG on Thu, Aug 22, 2002 at 12:42:22PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Aug 22, 2002 at 12:42:22 -0700, Johan Karlsson wrote: > Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi > Responsible-Changed-By: johan > Responsible-Changed-When: Thu Aug 22 12:40:51 PDT 2002 > Responsible-Changed-Why: > Over to -scsi since the proposal is to change cd0. Let's see if there are any opinions on freebsd-standards. The question is, what sort of error should we return from a peripheral driver (cd(4), da(4), etc.) open() routine when there is no media in the drive? Currently all CAM drivers will return ENXIO, and although the PR says that the acd(4) driver returns EIO, I can't tell from acdopen that it returns any errors at all if media isn't present. My guess is that EIO is getting returned sometime later in the acd(4) driver. (If that is still the case, this PR was filed in late 1999.) So is there any opinion on -standards as to what sort of error we should return on open if there is no media in a drive? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message