From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv3] toolchain: granular choice for stack protector
Date: Sun, 27 Dec 2015 12:45:25 +0100 [thread overview]
Message-ID: <20151227124525.763fcd14@free-electrons.com> (raw)
In-Reply-To: <CAKbGBLhQahOvac7XK7EWsQcK_6Um+j4_f0a+ZD3Td7sitpm9xg@mail.gmail.com>
Steven,
On Sun, 27 Dec 2015 03:39:19 -0800, Steven Noonan wrote:
> When SSP is *enabled* (BR2_ENABLE_SSP) the default should be
> BR2_SSP_STRONG (if available). It's generates code that's
> better-protected than BR2_SSP_REGULAR, but faster and smaller than
> BR2_SSP_ALL.
>
> Only crazy folks would use BR2_SSP_ALL if BR2_SSP_STRONG is an option. ;)
We want to preserve existing behavior as much as possible. So people
who enabled BR2_ENABLE_SSP were paying the price of BR2_SSP_ALL, and we
should therefore keep using BR2_SSP_ALL for such users. That's the
point of legacy handling: minimizing the amount of "surprise" /changes
for users upgrading Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-27 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 11:07 [Buildroot] [PATCHv3] toolchain: granular choice for stack protector Yann E. MORIN
2015-12-27 11:39 ` Steven Noonan
2015-12-27 11:44 ` Yann E. MORIN
2015-12-27 11:45 ` Thomas Petazzoni [this message]
2015-12-27 14:12 ` Steven Noonan
2015-12-27 14:34 ` Thomas Petazzoni
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=20151227124525.763fcd14@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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