linux-kernel - Re: [BUG] linux-next: Tree for April 9 warning on CC

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: <47FDF2DF.6030006@gmail.com>
Date:	Thu, 10 Apr 2008 12:58:39 +0200
From:	Jacek Luczak <difrost.kernel@...il.com>
To:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Andy Whitcroft <apw@...dowen.org>
Subject: Re: [BUG] linux-next: Tree for April 9 warning on CC_STACKPROTECTOR,
 followed by kernel panic

Kamalesh Babulal pisze:
> Jacek Luczak wrote:
>> Kamalesh Babulal pisze:
>>> Hi Stephen,
>>>
>>> The next-20080409 kernel warns while booting up on a x86_64 machine.
>>> When compiled the kernel with CONFIG_CC_STACKPROTECTOR=y, the warning
>>> is followed by the kernel panic.
>>>
>>> Testing -fstack-protector-all feature
>>> No -fstack-protector-stack-frame!
>>> -fstack-protector-all test failed
>>> ------------[ cut here ]------------
>>> WARNING: at kernel/panic.c:365 __stack_chk_test+0x4b/0x50()
>>> Modules linked in:
>>> Pid: 1, comm: swapper Not tainted 2.6.25-rc8-next-20080409-autotest #1
>>>
>>> Call Trace:
>>>  [<ffffffff80231f5e>] warn_on_slowpath+0x51/0x63
>>>  [<ffffffff80232d93>] printk+0x4e/0x56
>>>  [<ffffffff80382fcd>] extract_entropy+0x47/0x90
>>>  [<ffffffff80230000>] dup_mm+0xca/0x3fd
>>>  [<ffffffff80231eba>] __stack_chk_test_func+0x21/0x32
>>>  [<ffffffff80231fbb>] __stack_chk_test+0x4b/0x50
>>>  [<ffffffff808ba8f1>] kernel_init+0x189/0x2f9
>>>  [<ffffffff804ee221>] _spin_unlock_irq+0x9/0xc
>>>  [<ffffffff8020cb88>] child_rip+0xa/0x12
>>>  [<ffffffff808ba768>] kernel_init+0x0/0x2f9
>>>  [<ffffffff8020cb7e>] child_rip+0x0/0x12
>>>
>>> ---[ end trace d88d2f3a71e3b32c ]---
>> Hi,
>>
>> what version of GCC are you using?
>>
>> -Jacek
> Hi Jacek,
> 
> I use the gcc version (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)

IMO it's GCC problem (I've seen a lot of problems with stack-protector and GCC 4.1 branch). Can you make some tests with 
4.2 branch?

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