linux-kernel - Re: Major qla2xxx regression on sparc64

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20070418.131341.129061984.davem@davemloft.net>
Date:	Wed, 18 Apr 2007 13:13:41 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	andrew.vasquez@...gic.com
Cc:	hch@...radead.org, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org, James.Bottomley@...elEye.com,
	ema@...ian.org
Subject: Re: Major qla2xxx regression on sparc64

From: Andrew Vasquez <andrew.vasquez@...gic.com>
Date: Wed, 18 Apr 2007 10:28:02 -0700

> On Wed, 18 Apr 2007, Christoph Hellwig wrote:
> 
> > I don't think a module option is a good idea at this point.  The problem
> > is you broke some so far perfectly working setups, which is not okay.
> > The only first step can be printing a really big warning.  After this
> > has been in for a while (at lest half a year) we can make it a non-default
> > option or turn if off completely in case the warning never triggered in
> > practice.
> > 
> > The only resonable thing for 2.6.21 is to put in David's patch, possible
> > with an even more drastic warning when the rom is invalid and there's
> > no prom-fallback available.
> > 
> > Note that I expect Sun put in the invalid ROM intentionally, as we have
> > similar cases with other cards that have totally messed up ROMs in
> > Sun-branded versions.  Personally I think that's an utterly bad decision
> > from Sun's side, but we'll have to live with this.
> 
> Fine.  I'll rework an alternate patch for the 2.6.22 timeframe...

We need to fix things now for 2.6.21 and the 2.6.x -stable branches
because users have unusable systems currently.

If it's just a time issue I can work on and push the patch, especially
since I have the means to test things here.

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