linux-kernel - Re: linux 2.6.27 kernel panic on x86 - please revert commit 3a85e770aa77e4f1a4096275c97b64c10cd7323e

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, 15 Oct 2008 21:39:39 +0800
From:	"Jeff Chua" <jeff.chua.linux@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Suresh Siddha" <suresh.b.siddha@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"Jeremy Fitzhardinge" <jeremy@...p.org>
Subject: Re: linux 2.6.27 kernel panic on x86 - please revert commit 3a85e770aa77e4f1a4096275c97b64c10cd7323e

On Wed, Oct 15, 2008 at 8:05 PM, Ingo Molnar <mingo@...e.hu> wrote:
>> Unsetting CONFIG_COMPAT_VDSO solves the issue.
>>
>> Thanks for your help, and sorry for the fault alarm. Did take a while
>> to trace it down to the commit.
>
> hm, setting the option should not break new glibc so this is a
> regression and we've still got a bug to fix.

Something must have triggered the bug. Every single linux git update
has been ok with CONFIG_COMPAT_VDSO=y until now, and I had glibc-2.7
since Dec 2007.

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