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 1/2] stackprotector: add stack smashing protector generic implementation
Date: Thu, 6 Jan 2011 15:16:25 +0100	[thread overview]
Message-ID: <4D25CEB9.7090205@st.com> (raw)
In-Reply-To: <20110106093940.GA31708@n2100.arm.linux.org.uk>

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

On 1/6/2011 10:39 AM, Russell King - ARM Linux wrote:
> On Wed, Jan 05, 2011 at 12:59:18PM +0100, Carmelo AMOROSO wrote:
>  > Is someone interested into this stuff ?
> 
> Looking at the CC list, you're asking the people who already have the
> support in the kernel. I suspect they don't have that much of an
> interest in it.
> 
> Maybe you should try asking other architecture maintainers who don't
> support this yet? Not every architecture maintainer is subscribed to,
> or reads LKML...
> 

Hi Russel, thanks for your feedback.
Well, SH (in CC) does not have this support. Indeed we posted it
initially to linux-sh only. We got useful feedback from Paul, Mike and
Nicolas suggesting to promote the ARM/SH solution based on the global
__stack_chk_guard variable as a generic solution for all other
architectures. This is why I thought to post to the LKML instead of each
linux-<arch> list.
The code is able to detect if the arch implementation is based on the
global (if so the generic implementation should work cleanly), otherwise
it will fail to compile when trying to include the
linux/asm/stackprotector.h. This is an easy way to detect the lack of an
arch specific implementation (but likely only x86 needs it... I don't know).

So the idea is to use the ARM code as generic's one (tested on SH
kernel). Mike Frysinger volunteered to try on blackfin for example.

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

iEYEARECAAYFAk0lzrkACgkQoRq/3BrK1s/JhACdERr4TFBaGmf4XuQEUA/9X/Kt
lz4An0fctncE+n9fhHvvZEbIZEilJKNO
=5yFm
-----END PGP SIGNATURE-----

  reply	other threads:[~2011-01-06 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23 13:44 [PATCH 1/2] stackprotector: add stack smashing protector generic implementation Filippo ARCIDIACONO
2010-12-23 13:44 ` [PATCH 2/2] sh: stackprotector: change the canary value per task Filippo ARCIDIACONO
2011-01-05 11:59 ` [PATCH 1/2] stackprotector: add stack smashing protector generic implementation Carmelo AMOROSO
2011-01-06  9:39   ` Russell King - ARM Linux
2011-01-06 14:16     ` Carmelo AMOROSO [this message]
2011-01-06 14:19       ` Russell King - ARM Linux
2011-01-06 14:43         ` Carmelo AMOROSO
2011-01-11  5:30   ` Mike Frysinger
2011-01-11 15:56     ` Carmelo AMOROSO

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=4D25CEB9.7090205@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).