linux-kernel - Re: [tip:x86/asm] x86: Detect stack protector for i386 builds on x86

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: <20090901100351.GA3361@elte.hu>
Date:	Tue, 1 Sep 2009 12:03:51 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	arjan@...radead.org, jeremy@...p.org, mschmidt@...hat.com,
	mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	tj@...nel.org, tglx@...utronix.de
Cc:	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/asm] x86: Detect stack protector for i386 builds on
	x86_64


* tip-bot for Michal Schmidt <mschmidt@...hat.com> wrote:

> Commit-ID:  23386d63bbb3199cf247313ec088878d72debcfd
> Gitweb:     http://git.kernel.org/tip/23386d63bbb3199cf247313ec088878d72debcfd
> Author:     Michal Schmidt <mschmidt@...hat.com>
> AuthorDate: Sat, 29 Aug 2009 18:27:18 +0200
> Committer:  Ingo Molnar <mingo@...e.hu>
> CommitDate: Sun, 30 Aug 2009 20:39:48 +0200
> 
> x86: Detect stack protector for i386 builds on x86_64

FYI, -tip testing found a nasty bootup crash:

[    0.027010] Checking 'hlt' instruction... OK.
[    0.034023] calling  spawn_ksoftirqd+0x0/0x48 @ 1
[    0.035025] BUG: unable to handle kernel NULL pointer dereference at (null)
[    0.035994] IP: [<c102c79a>] try_to_wake_up+0x2f/0x174
[    0.035994] *pde = 00000000 
[    0.035994] Oops: 0000 [#1] DEBUG_PAGEALLOC
[    0.035994] last sysfs file: 

and i bisected it down to this commit. The crash was probably 
pre-existing - stackprotector was not enabled in this type of 
cross-build i did.

crashlog and config attached.

Note that 32-bit defconfig + CONFIG_STACKPROTECTOR works just fine - 
so it's some other detail that triggers this crash.

	Ingo

View attachment "config" of type "text/plain" (69206 bytes)

View attachment "crash.log" of type "text/plain" (16616 bytes)