From: Carmelo AMOROSO <carmelo.amoroso@st.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Filippo ARCIDIACONO <filippo.arcidiacono@st.com>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"nicolas.pitre@linaro.org" <nicolas.pitre@linaro.org>,
"nico@fluxnic.net" <nico@fluxnic.net>
Subject: Re: [PATCH 1/2] stackprotector: add stack smashing protector generic implementation
Date: Tue, 11 Jan 2011 16:56:02 +0100 [thread overview]
Message-ID: <4D2C7D92.1090104@st.com> (raw)
In-Reply-To: <AANLkTinZCDRVwwchcB85Wock8nBYK1eJrTWPbgJ-roGh@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 945 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/11/2011 6:30 AM, Mike Frysinger wrote:
> what are you using to test this ? is there a simple strcpy or similar
> code you run as a kernel module that'll allow me to verify ?
> -mike
>
Hi Mike,
yes, a simple kernel module with a init func that use strcpy or memcpy
to write over the boundaries of an local array variable is enough.
As you know, the array has to be larger than 8 bytes to match with the
gcc heuristic and generate the call to the guard.
Cheers,
Carmelo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk0sfZIACgkQoRq/3BrK1s8kfwCeIjayIoaHapweG53icp1yoCN+
ypMAnA08chxTu49eP4QYTQU8UzO4PVpp
=ysi4
-----END PGP SIGNATURE-----
ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
prev parent reply other threads:[~2011-01-11 15:56 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
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 [this message]
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=4D2C7D92.1090104@st.com \
--to=carmelo.amoroso@st.com \
--cc=filippo.arcidiacono@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=nicolas.pitre@linaro.org \
--cc=vapier@gentoo.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