linux-kernel - Re: [PATCH] libata: rewrite SCSI host scheme to be one per ATA host

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <49F19BE1.6030104@s5r6.in-berlin.de>
Date:	Fri, 24 Apr 2009 13:00:49 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Grant Grundler <grundler@...gle.com>
CC:	Jeff Garzik <jeff@...zik.org>, linux-ide@...r.kernel.org,
	linux-scsi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] libata: rewrite SCSI host scheme to be one per ATA host

Grant Grundler wrote:
> Data Center
> environments (not just Google's) like to track disks in many different
> ways, including the SCSI identifiers since this one "key" for physical
> location. Breaking the current mappings is going to cause some people
> a world of pain

If by SCSI identifiers you mean the Linux SCSI core's h:c:i:l, then
remember that these are scsi-core internal artifacts without any meaning
to lower and upper layers whatsoever, including userspace.  (Exception:
 The c:i:l part has some significance with SCSI Parallel Interface
attached hardware.)

> since they will need to manually build (and integrate)
> old->new maps of the SCSI identifiers.

Stock udev already provides mapping according to actually useful
identifiers (if the respective transport provides them: persistent and
unique identifiers of targets and logical units).
-- 
Stefan Richter
-=====-==--= -=-- ==---
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/