| 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
| ||
|
Message-ID: <0F5B06BAB751E047AB5C87D1F77A778826B3DD7474@GVW0547EXC.americas.hpqcorp.net> Date: Thu, 24 Jul 2008 15:00:00 +0000 From: "Miller, Mike (OS Dev)" <Mike.Miller@...com> To: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>, "scameron@...rdog.cca.cpqcorp.net" <scameron@...rdog.cca.cpqcorp.net> CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org> Subject: RE: HP (Compaq) Smart Array 5xxx controller SCSI driver > > As for the patches I mentioned which were previously ignored for > > improving how the current cciss SCSI code handled hot plogging, if > > you're curious about that, check here: > > > > http://marc.info/?l=linux-scsi&m=120213565000426&w=4 > > > > A change like that becomes more important if logical drives are > > exposed through the scsi layer. > > We need to think about the best way to map (expose) logical > and physical drivers to SCSI luns. As I wrote before, I'm > interested in how HP SCSI driver does. We don't neccesarily want or need to expose the physical disks. The only exception is disks that are not part of a logical volume. If the disks are part of a logical volume but exposed the user may shoot themselves in the foot by destroying the firmware metadata. -- mikem -- 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/
Powered by blists - more mailing lists