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]
Message-Id: <20080724095325F.fujita.tomonori@lab.ntt.co.jp>
Date:	Thu, 24 Jul 2008 10:32:42 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	Mike.Miller@...com
Cc:	fujita.tomonori@....ntt.co.jp, iss_storagedev@...com,
	James.Bottomley@...senPartnership.com, Jens.Axboe@...cle.com,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: RE: [RFC PATCH] HP (Compaq) Smart Array 5xxx controller SCSI driver

On Wed, 23 Jul 2008 14:07:39 +0000
"Miller, Mike (OS Dev)" <Mike.Miller@...com> wrote:

> > > > If I can get an ACK from HP about the long-term migration
> > of cciss
> > > > to SCSI, I'm happy to keep working on the SCSI cciss driver and
> > > > maintain it until HP takes over the driver.
> > >
> > > We already have a SCSI port of the driver that is at least as
> > > functional as you decribe. But I am against it's release for the
> > > reasons stated above. If we ever decide to release the SCSI port it
> > > should be developed by HP so we can be assured that the utils and
> > > agents work as expected. That doesn't mean we wouldn't
> > leverage some
> > > of your work. ;)
> >
> > If HP releases its SCSI driver, I'm happy to throw my driver
> > away and work on HP SCSI driver. I like to see a driver in
> > development rather than a finished driver; development in
> > mainline rather than private development at a vendor.
> > Everyone can see the progress and try it.
> 
> We'll post something sooner rather than later.

Nice! When are you likely to release the driver?

One thing that I'm interested in is how you map CCISS logical and
physical units to SCSI logical unit numbers. During writing a patch,
I've been thinking about what's the best way for users.


> I've been hesitant to submit unfinished work but I guess having the
> community provide input along the way is the best way to go.

Yeah, I'm happy to polish the driver even if I can't compile it.


> OK, Tomo, you win!   :)

Thanks a lot for agreeing to move the CCISS driver to SCSI!

I know that there are several other people who are really pleased with
the decision.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ