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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 06 May 2008 12:49:33 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Kevin Winchester <kjwinchester@...il.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: linux-next: WARNING: at kernel/panic.c:375 __stack_chk_test+0x50/0x54()

Kevin Winchester wrote:
> Arjan van de Ven wrote:
>> \
>>> Does that help?
>>
>> somewhat. If you still have your source tree, can you do
>>
>> make kernel/panic.s and send that file to me as well?
>> (offlist is fine)
>>
> 
> I didn't have the source tree around, but I created the tree+config, and 
> here is what I get (I believe it is not too big for the list):
> 

interesting; somehow gcc does NOT put stack-protector in place despite it being
told so with -fstack-protector-all.

# -fno-common -funit-at-a-time -fstack-protector -fstack-protector-all
# -fno-asynchronous-unwind-tables -fno-omit-frame-pointer
# -fno-optimize-sibling-calls -fverbose-asm -fstack-protector
# -fstack-protector


this is weird; something is adding ANOTHER -fstack-protector to the (effective) gcc
flags.. which might be overriding the -fstack-protector-all setting.

I wonder if this is a distro special ;(
--
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/