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] [day] [month] [year] [list]
Message-ID: <20080602185740.GA18550@elte.hu>
Date:	Mon, 2 Jun 2008 20:57:40 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Thomas Meyer <thomas@...3r.de>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: linux-next: Tree for May 30


* Thomas Meyer <thomas@...3r.de> wrote:

> Zitat von Ingo Molnar <mingo@...e.hu>:
> 
> > hm, that commit is gone in latest tip - does tip/master boot fine for 
> > you? It's:
> > 
> >    http://people.redhat.com/mingo/tip.git/README
> > 
> > that commit was an interim fix that got removed meanwhile and replaced 
> > with the real fixes.
> 
> I just booted next-20080602 successfully, and the latest commit on 
> file arch/x86/kernel/setup_32.c is:
> 
> 4efc5450e19128e0c77fbfdf4a14804f5a4a1d95 (Merge branch 'x86/numa' into 
> auto-x86-next).
> 
> So yes, the original commit causing the error for me is gone.

thanks for testing it and it's great that the crash is gone!

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