linux-kernel - Re: INITIO scsi driver fails to work properly

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: <1197903781.3204.4.camel@localhost.localdomain>
Date:	Mon, 17 Dec 2007 09:03:01 -0600
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Boaz Harrosh <bharrosh@...asas.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Filippos Papadopoulos <psybases@...il.com>,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: INITIO scsi driver fails to work properly


On Mon, 2007-12-17 at 14:36 +0000, Alan Cox wrote:
> On Mon, 17 Dec 2007 16:40:53 +0200
> Boaz Harrosh <bharrosh@...asas.com> wrote:
> 
> > On Mon, Dec 17 2007 at 15:05 +0200, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > >> initio doesn't seem to have a maintainer...
> > >>
> > >> Are you able to identify any earlier kernel which worked OK?
> > >>
> > >> Maybe it's a new device?  If you can get the `lspci -vvxx' output
> > >> for that device we can take a look.
> > > 
> > > If I remember rightly the fixes for this went into the scsi tree a couple
> > > of months ago. The patch is in the -mm tree as well. No idea why its
> > > gotten stuck as an obvious one liner.
> > > 
> > > Alan
> > > -
> > You mean this one:
> > http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commitdiff;h=ba2c270154cc90c9a8bfc45b7bed4cca78c75aaf
> > 
> > It's only queued for 2.6.25 via scsi-misc.
> > 
> > I have found another bug. (See other mail in thread). I Will wait for testing
> > and submit a proper patch.
> 
> That one yes - which really should have gone straight into the main tree
> as the initio driver has been broken all the time it sits queued for
> future patches. It can't make the problem any worse - the driver does not
> work.

Well, the change log isn't very committal for "rush me immediately into
main line" plus, as far as I could dig out, there was no confirmation
that it actually worked.  This way, I can now say please try the current
-mm kernel to the bug reporter and we get to see if this fixes the
problem.

James


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