linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: carmelo.amoroso@st.com (Carmelo AMOROSO)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH (sh-2.6) 1/2] sh: add stack smashing protection support
Date: Thu, 9 Dec 2010 17:45:30 +0100	[thread overview]
Message-ID: <4D0107AA.2020909@st.com> (raw)
In-Reply-To: <201012091107.51911.vapier@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/9/2010 5:07 PM, Mike Frysinger wrote:
> On Thursday, December 09, 2010 10:56:26 Carmelo AMOROSO wrote:
>> I agree with you that the Kconfig and Makefile changes are not arch
>> specific, so these changes can be moved to a common code (even if I
>> don't know if other archs do support SSP).
>> In the current kernel, only x86 and ARM added this support, so I'm
>> wondering if, moving SSP to the common Makefile, it needs to depend on
>> x86, ARM, SH being configured ?
> 
> i'm not sure it does.  ssp is designed to be arch independent, so really you 
> only need a new enough gcc version.  which means i dont think it needs to 
> depend on any arch code and you can simply add to the Makefile a compiler 
> check.
> 
agreed, but if arch wants to implement the per-task canary feature, some
change into arch specific code is required.

>> Regarding the __stack_chk_guard symbol defined in process[_32].c, I
>> don't know if all archs need to define this global variable to implement
>> SSP. For sure x86 does not need it. It depends on how the gcc implements
>> this feature. This was mainly the reason for which we defined it
>> specifically in an arch specific code.
> 
> the common gcc code too outputs __stack_chk_guard references.  none of that is 
> in arch-specific places.

a simple test on x86 just prints reference to __stack_chk_fail only (not
reference to the global variable guard)

gcc is 4.3.0-8 (Fedora C9)

> -mike

carmelo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0BB6oACgkQoRq/3BrK1s8UCwCgwZWzH68RsmMiwWYn13f0+g30
+QAAn10EkbDLYZY1qmkTKd/OLF68+rlL
=Xq83
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-12-09 16:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 10:20 [PATCH (sh-2.6) 1/2] sh: add stack smashing protection support Filippo ARCIDIACONO
2010-12-07 10:20 ` [PATCH (sh-2.6) 2/2] arm: use generic implementation of boot_init_stack_canary Filippo ARCIDIACONO
2010-12-07 18:29   ` Nicolas Pitre
2010-12-07 13:43 ` [PATCH (sh-2.6) 1/2] sh: add stack smashing protection support Uwe Kleine-König
2010-12-07 18:28 ` Nicolas Pitre
2010-12-07 20:15 ` Mike Frysinger
2010-12-08  4:40   ` Paul Mundt
2010-12-09 15:56     ` Carmelo AMOROSO
2010-12-09 16:07       ` Mike Frysinger
2010-12-09 16:45         ` Carmelo AMOROSO [this message]
2010-12-09 17:32           ` Mike Frysinger
2010-12-09 18:23             ` Nicolas Pitre
2010-12-09 18:52               ` Carmelo Amoroso
2010-12-09 21:14               ` Mike Frysinger
2010-12-10  5:56                 ` Carmelo AMOROSO
2010-12-10  6:38                   ` Mike Frysinger

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=4D0107AA.2020909@st.com \
    --to=carmelo.amoroso@st.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).