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: <48190844.5080804@linux.intel.com>
Date:	Wed, 30 Apr 2008 17:01:08 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Kevin Winchester <kjwinchester@...il.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: linux-next: WARNING: at kernel/panic.c:375 __stack_chk_test+0x50/0x54()

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ