Re: kernel compiled with STACKPROTECTOR_ALL

"Gilles Espinasse" <[email protected]>
Newsgroups gmane.comp.security.ipcop.devel
Message-ID <050f01cbd0ee$f469a830$f9b5a8c0@pii350>
----- Original Message ----- 
From: "Gilles Espinasse" <[email protected]>
To: "IPCOP devel" <[email protected]>
Sent: Saturday, February 05, 2011 5:00 PM
Subject: Re: kernel compiled with STACKPROTECTOR_ALL


I find some more explanation on stackprotector-all overhead at
http://osdir.com/ml/linux-kernel/2009-10/msg07064.html
Reading the entire post is interesting.

Just checking our compiled files, I found that the vmlinuz file (lzma
compressed) is 10% larger with -fstack-protector-all than
with -fstack-protector-all. Comparing compressed/vmlinux.bin size (the file
before before lzma compression), the difference is 390 kB.

It may be not easy to compile the kernel with only -fstack-protector
when -fstack-protector-all is hardcoded to gcc default.
I haven't tested but I suppose that may not work to add
'-fno-stack-protector -fstack-protector' to CFLAGS_KERNEL.
Unsure that may broke parts requiring -fno-stack-protector usage if this not
appended last.
So the question is do we really need a hardcoded default
with -fstack-protector-all?

Would you be ok to change gcc default setting to use -fstack-protector only
by default?

Gilles


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.