public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 30 Apr 2008 17:01:08 -0700	[thread overview]
Message-ID: <48190844.5080804@linux.intel.com> (raw)
In-Reply-To: <4819078C.9080405@gmail.com>

Kevin Winchester wrote:
> 
> Hi Arjan,
> 
> There doesn't seem to be an entry in MAINTAINERS for stack protector, 
> but your signoff was on the last stack protector related commit I could 
> find, so it's probably a good bet.
> 
> I get the following in my dmesg after testing linux-next with the stack 
> protector turned on.  This is an x86-64 UP box if that helps.  It 
> appears to be related to the test for the feature (or perhaps that is 
> supposed to happen when the feature is tested, I'm not sure...).  Config 
> below.
> 

the important question is: exactly what gcc are you using? (and if you use a distro gcc,
which distro)

second question would be, what does the following command give?

echo "int foo(void) { char X[200]; return 3; }" | $1 -S -xc -c -O0 -mcmodel=kernel -fstack-protector - -o -

(this is the command from scripts/gcc-x86_64-has-stack-protector.sh that the kernel uses to test at compiletime
  if you have stack protector support)

  reply	other threads:[~2008-05-01  0:03 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 [this message]
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
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=48190844.5080804@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox