linux-kernel - Re: linux-next: WARNING: at kernel/panic.c:375 __stack_chk

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]

Date:	Tue, 06 May 2008 16:38:18 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Kevin Winchester <kjwinchester@...il.com>
CC:	David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
	mingo@...e.hu
Subject: Re: linux-next: WARNING: at kernel/panic.c:375 __stack_chk_test+0x50/0x54()

Kevin Winchester wrote:
> -march=k8 -mno-red-zone -mcmodel=kernel -funit-at-a-time 
> -maccumulate-outgoing-args -fstack-protector -DGCC_HAS_SP 
> -fstack-protector-all   -pipe -Wno-sign-compare 
   ^^^^^^^^^^^^^^^^^^^^^^
> -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow 
> -Iinclude/asm-x86/mach-default -fno-omit-frame-pointer 
> -fno-optimize-sibling-calls -g -pg -Wdeclaration-after-statement 
> -Wno-pointer-sign     -D"KBUILD_STR(s)=#s" 


the kernel makefiles are doing exactly the right things....
yet your previous data showed that something adds a -fstack-protector
after it.... grrr.

Sounds like I need to figure how to make a testcase for this that we
can then use to, at build time, detect this b0rked gcc behavior.

thanks a lot for helping me diagnosing this so far!

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