From: Arjan van de Ven <arjan@linux.intel.com>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next: WARNING: at kernel/panic.c:375 __stack_chk_test+0x50/0x54()
Date: Tue, 06 May 2008 12:49:33 -0700 [thread overview]
Message-ID: <4820B64D.4000805@linux.intel.com> (raw)
In-Reply-To: <481CF3B1.2020307@gmail.com>
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 ;(
next prev parent reply other threads:[~2008-05-06 19:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 23:58 linux-next: WARNING: at kernel/panic.c:375 __stack_chk_test+0x50/0x54() Kevin Winchester
2008-05-01 0:01 ` Arjan van de Ven
2008-05-01 0:24 ` Kevin Winchester
2008-04-30 7:27 ` Arjan van de Ven
2008-05-01 22:37 ` Kevin Winchester
2008-05-01 11:33 ` Arjan van de Ven
2008-05-03 23:22 ` Kevin Winchester
2008-05-06 19:49 ` Arjan van de Ven [this message]
2008-05-06 20:34 ` David Miller
2008-05-06 23:09 ` Kevin Winchester
2008-05-06 23:10 ` Arjan van de Ven
2008-05-06 23:32 ` Arjan van de Ven
2008-05-06 23:35 ` Kevin Winchester
2008-05-06 23:38 ` Arjan van de Ven
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=4820B64D.4000805@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.