Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Romain Naour <romain.naour@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] toolchain: make paranoid check of library/header paths unconditional
Date: Sun, 5 Feb 2023 15:12:42 +0100	[thread overview]
Message-ID: <20230205141242.GI2960@scaer> (raw)
In-Reply-To: <20230205150023.105dfc14@windsurf>

All,

On 2023-02-05 15:00 +0100, Thomas Petazzoni via buildroot spake thusly:
> On Mon,  7 Nov 2022 22:49:03 +0100
> "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > When we introduced support for the paranoid check of unsafe libraries
> > and headers path with commit 4ac8f78d3771 (Add option for paranoid
> > unsafe path checking) back in 2014, we made it optional, as we expected
> > that would break quite a few packages.
[--SNIP--]
> > It is time to make that globally unconditional now.
> > 
> > There is still a remnant, in our binutils patches. As our toolchain may
> > get used outside of Buildroot, people may got the expectation that path
> > poisoning is only a warning, so we keep the current behaviour.
> > 
> > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> > Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> > Cc: Romain Naour <romain.naour@gmail.com>
> > ---
> >  Config.in                               | 18 ------------------
> >  package/Makefile.in                     |  3 +--
> >  support/config-fragments/minimal.config |  1 -
> >  toolchain/toolchain-wrapper.c           | 21 ++++-----------------
> >  4 files changed, 5 insertions(+), 38 deletions(-)
> 
> Acked-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Applied to master, thanks.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-02-05 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 21:49 [Buildroot] [PATCH] toolchain: make paranoid check of library/header paths unconditional Yann E. MORIN
2023-02-05 14:00 ` Thomas Petazzoni via buildroot
2023-02-05 14:12   ` 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=20230205141242.GI2960@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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