All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] toolchain: granular choice for stack protector
Date: Sun, 27 Dec 2015 11:55:18 +0100	[thread overview]
Message-ID: <20151227105518.GD3483@free.fr> (raw)
In-Reply-To: <CAKbGBLgU3woN+OEPF3tDUO7xs1XdUrFk2i10qdY1x=wF-EBZdw@mail.gmail.com>

Steven, All,

On 2015-12-27 02:44 -0800, Steven Noonan spake thusly:
> On Sun, Dec 27, 2015 at 2:26 AM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > On 2015-12-27 11:19 +0100, Thomas Petazzoni spake thusly:
> >> On Sun, 27 Dec 2015 00:42:06 +0100, Yann E. MORIN wrote:
> >> > -config BR2_ENABLE_SSP
> >> > +choice
> >> >     bool "build code with Stack Smashing Protection"
> >> > -   depends on BR2_TOOLCHAIN_HAS_SSP
> >> > +   default BR2_SSP_ALL if BR2_ENABLE_SSP # legacy
> >> > +   default BR2_SSP_STRONG if BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
> >>
> >> I don't understand this part. Why would we now defalut on
> >> BR2_SSP_STRONG if gcc >= 4.9 ?
> >
> > Hmmm... I did not think too much about that. I just "updated" the patch
> > and kept its meaning as-is.
> >
> >> I think we should keep the default of not having SSP enabled.
> >
> > Yes, makes sense. At best, the change in the default should have been in
> > another patch.
> 
> I could be wrong, but I *think* BuildRoot used to default to SSP on.
> If not, I don't know why I would have changed the default. I'm not a
> particularly big fan of SSP to begin with, so I'd have no incentive to
> default it enabled.

OK, so I will definitely remove the new defaults before I respin.

Thanks for the feedback! :-)

Regards,
Yann E. MORIN.

> > I'll fix and respin.
> >
> > Regards,
> > Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2015-12-27 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-26 23:42 [Buildroot] [PATCHv2] toolchain: granular choice for stack protector Yann E. MORIN
2015-12-27  0:27 ` Steven Noonan
2015-12-27  9:23   ` Yann E. MORIN
2015-12-27 10:19 ` Thomas Petazzoni
2015-12-27 10:26   ` Yann E. MORIN
2015-12-27 10:44     ` Steven Noonan
2015-12-27 10:55       ` Yann E. MORIN [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=20151227105518.GD3483@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.