Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752687Ab1FRTka (ORCPT ); Sat, 18 Jun 2011 15:40:30 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:43046 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752610Ab1FRTk1 (ORCPT ); Sat, 18 Jun 2011 15:40:27 -0400 Subject: Re: [PATCH 1/3] [RFC] genhd: add a new attribute in device structure From: James Bottomley To: Greg KH Cc: Kay Sievers , Nao Nishijima , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, jcm@redhat.com, hare@suse.de, stefanr@s5r6.in-berlin.de, yrl.pp-manager.tt@hitachi.com In-Reply-To: <20110617162247.GA16261@kroah.com> References: <20110616181943.GB1439@kroah.com> <1308256290.2436.143.camel@mulgrave> <1308264321.2436.161.camel@mulgrave> <1308320844.2586.14.camel@mulgrave> <1308322193.2586.30.camel@mulgrave> <20110617162247.GA16261@kroah.com> Content-Type: text/plain; charset="UTF-8" Date: Sat, 18 Jun 2011 14:40:17 -0500 Message-ID: <1308426017.2586.1273.camel@mulgrave> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 (2.30.3-1.fc13) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2427 Lines: 53 On Fri, 2011-06-17 at 09:22 -0700, Greg KH wrote: > On Fri, Jun 17, 2011 at 06:12:14PM +0200, Kay Sievers wrote: > > On Fri, Jun 17, 2011 at 17:39, Kay Sievers wrote: > > > On Fri, Jun 17, 2011 at 16:49, James Bottomley > > > > >> So this is subsystem specific. For the case of a SCSI enclosure, I can > > >> answer that it's actually burned into the enclosure firmware. When you > > >> build an enclosure with labels, the label names are stored in a > > >> diagnostic page. We can actually interrogate the enclosure directly or > > >> use the ses driver to get these names mapped to current devices. > > > > > > To me this sounds like a nice name on top of the current bunch of > > > names, not like a 'preferred' name. > > > > > > I still don't like to introduce any new facility to the kernel that > > > can handle only one single name. Reality the last years has taught us > > > a very different story, and we've walked a long way to get where we > > > are. I really don't believe single names will ever work, it's just a > > > nice theory. > > > > I might need to clarify this a bit. > > > > I have no problem in general to add a 'alias' to every disk, and use > > that when stuff is logged. Just the same way the netifs have an alias. > > Sure, it might be useful for some use cases. And if that helps to > > solve any real problem, we should just do it. > > > > I just want to make clear, that I don't think that it is anywhere near > > to a solution for the problems which are described here. And that > > nobody should see this as an excuse not to get their stuff together > > and work on the problem, which is that we don't have machine-readable > > error and debug from the kernel and a smart syslog. > > > > If we had that, I'm very sure nobody would even ask for a 'pretty > > name' in the kernel, and I think that is a good indication that we are > > not on the right track here. > > And I totally agree here, which is why I don't want to accept this > change to the driver core to add this, as it's not the correct solution. OK, fine ... we'll do it as gendisk only then. I suppose that is the 95% use case anyway. Thanks, James -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/