linux-kernel - Re: HP (Compaq) Smart Array 5xxx controller SCSI driver

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 24 Jul 2008 08:30:12 -0500
From:	scameron@...rdog.cca.cpqcorp.net
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	scameron@...rdog.cca.cpqcorp.net, mike.miller@...com
Subject: Re: HP (Compaq) Smart Array 5xxx controller SCSI driver

On Thu, Jul 24, 2008 at 10:32:45AM +0900, FUJITA Tomonori wrote:
> CC'ed linux-scsi, why did you drop it?

You mean my SCSI cciss driver?  For a few reasons:

At the time, it was just kind of a learning exercise, and I
didn't see it as supplanting the existing driver.  I didn't know
enough about udev to know that a smooth transition process
was perhaps possible, and it seemed very disruptive.  And,
seeing as how I work for HP, it isn't exactly within my
authority to just decide by myself the course the driver
development should take.  Paradoxically, if a person works
for a company that has nothing to do with the driver, one
has more freedom to do whatever one wants with the code.

With help from udev it is less disruptive, but I'm still unsure
about how smoothly such a change will fit in with the installation 
process of various distributions.

I will see if management here will let me send you the patches 
from when I last looked at this, which was a little over a year ago.
(2.6.20 timeframe), not necessarily to use as is, but in case
maybe it helps to see how somebody else proceeded. 

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.

-- steve

--
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/