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 16:10:28 -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:
> David Miller wrote:
>> From: Arjan van de Ven <arjan@...ux.intel.com>
>> Date: Tue, 06 May 2008 12:49:33 -0700
>>
>>> 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 ;(
>>
>> Ubuntu adds -fstack-protector to the GCC command line.
>>
>> But I've been able to override it trivially when, for example, doing
>> GCC builds, by simply adding -fno-stack-protector.
> 
> I assume adding -fno-stack-protector would not really be an option in 
> this case (since if I understand correctly it would be appended to the 
> end of the flags which would turn the option off).

yeah that's counter productive ;)

> 
> I guess I'll be figuring out how to build my own gcc...

well hold on a second ;)

I'd like to do a few more experiments, but if this is really an ubuntu special thing
I'd like to at least get the ubuntu gcc folks involved.
--
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/