public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacek Luczak <difrost.kernel@gmail.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Andy Whitcroft <apw@shadowen.org>
Subject: Re: [BUG] linux-next: Tree for April 9 warning on CC_STACKPROTECTOR, followed by kernel panic
Date: Thu, 10 Apr 2008 12:58:39 +0200	[thread overview]
Message-ID: <47FDF2DF.6030006@gmail.com> (raw)
In-Reply-To: <47FDF11D.40407@linux.vnet.ibm.com>

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

  reply	other threads:[~2008-04-10 11:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  8:53 linux-next: Tree for April 9 Stephen Rothwell
     [not found] ` <d711229d0804090400p1c92a158j381b86e207a6f38a@mail.gmail.com>
2008-04-09 11:09   ` Stephen Rothwell
2008-04-09 11:27     ` Stephen Rothwell
2008-04-09 11:26       ` Jacek Luczak
2008-04-09 11:34         ` Ingo Molnar
2008-04-09 11:55           ` Jacek Luczak
2008-04-09 12:01           ` Ingo Molnar
2008-04-09 11:31       ` Ingo Molnar
2008-04-09 14:50         ` Cyrill Gorcunov
2008-04-09 15:03           ` Ingo Molnar
2008-04-09 15:18             ` Cyrill Gorcunov
2008-04-09 16:55 ` Stefan Richter
2008-04-10  0:45   ` Stephen Rothwell
2008-04-10  6:52   ` Ingo Molnar
2008-04-10  7:44     ` Stephen Rothwell
2008-04-10  7:52       ` debug Kconfig option (was Re: linux-next: Tree for April 9) Stefan Richter
2008-04-10  9:51         ` Ingo Molnar
2008-04-10 19:05           ` [PATCH linux1394-2.6.git] firewire: fw-ohci: add option for remote debugging - amendment Stefan Richter
2008-04-10 22:08             ` Stefan Richter
2008-04-10 15:01         ` debug Kconfig option (was Re: linux-next: Tree for April 9) Randy Dunlap
2008-04-10  9:48       ` linux-next: Tree for April 9 Ingo Molnar
2008-04-10 19:02         ` Stefan Richter
2008-04-10  9:39 ` [BUG] linux-next: Tree for April 9 warning on CC_STACKPROTECTOR, followed by kernel panic Kamalesh Babulal
2008-04-10 10:14   ` Jacek Luczak
2008-04-10 10:51     ` Kamalesh Babulal
2008-04-10 10:58       ` Jacek Luczak [this message]
2008-04-10 11:47   ` Stephen Rothwell
2008-04-11  9:45     ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47FDF2DF.6030006@gmail.com \
    --to=difrost.kernel@gmail.com \
    --cc=apw@shadowen.org \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox