From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751450AbWC0Tre (ORCPT ); Mon, 27 Mar 2006 14:47:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751448AbWC0Trd (ORCPT ); Mon, 27 Mar 2006 14:47:33 -0500 Received: from [81.2.110.250] ([81.2.110.250]:13514 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1751447AbWC0Trd (ORCPT ); Mon, 27 Mar 2006 14:47:33 -0500 Subject: Re: [PATCH] Move SG_GET_SCSI_ID from sg to scsi From: Alan Cox To: Linus Torvalds Cc: Matthew Wilcox , Douglas Gilbert , Bodo Eggert <7eggert@gmx.de>, linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org In-Reply-To: References: <4427FEC9.4010803@torque.net> <20060327172530.GH3486@parisc-linux.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 27 Mar 2006 20:54:47 +0100 Message-Id: <1143489287.4970.76.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Llu, 2006-03-27 at 09:43 -0800, Linus Torvalds wrote: > The fact is, BUS/ID/LUN crap really doesn't make sense for the majority of > devices out there. Never has, never will. The fact that old-fashioned SCSI > devices think of themselves that way has absolutely zero to do with > reality today. It is still a very visible reality if you work in a data centre or with server kit, or if you have tape arrays or multi-CD towers. The LUN or device number in particular are generally the number emblazoned on each slot in the unit and knowing the LUN reliably is sort of critical to not making embarrasing (and career limiting) screwups when swapping drives. Controller is a pretty abstract concept and except on arrays so is device, but both device and LUN do need to be accessible reliably for the hardware that thinks that way. What other hardware does is irrelevant and "-EINVAL" seems as good an answer as anything. Alan