linux-kernel - Re: [PATCH] prom_find_machine_type typo breaks pSeries lpar boot

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:	Wed, 14 Nov 2007 13:37:33 -0600
From:	Nathan Lynch <ntl@...ox.com>
To:	"B. N. Poornima" <poornima@...ibm.com>
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Andrew Morton <akpm@...l.org>,
	Linus Torvalds <torvalds@...l.org>,
	ppc64 dev list <linuxppc64-dev@...abs.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Martin J. Bligh" <mbligh@...igh.org>, roland@...spin.com
Subject: Re: [PATCH] prom_find_machine_type typo breaks pSeries lpar boot

Hi-

B. N. Poornima wrote:
> >On Fri, 2005-06-03 at 14:25 -0500, Nathan Lynch wrote:
> >  
> >>Typo in prom_find_machine_type from Ben's recent patch "ppc64: Fix
> >>result code handling in prom_init" prevents pSeries LPAR systems from
> >>booting.
> >>
>
> Hello,
> Same typo has creped in again from 2.6.17 kernel onwards and causing 
> open firmware exception in pSeries systems.

Looking at the current code, I don't see how this analysis could be
correct.

> The patch that is provided solves the problem.

Which patch?  Did you forget to include it?

It would be best if you sent your problem report and any patches to
linuxppc-dev@...abs.org.  linuxppc64-dev is dead.

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