Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] gcc-9.2: Security fix for CVE-2019-14250
Date: Mon, 2 Sep 2019 15:40:03 +0300	[thread overview]
Message-ID: <20190902124003.GA8291@localhost> (raw)
In-Reply-To: <9b09243d-86b7-b358-e0be-c41f8acbcd47@gmail.com>

On Sun, Sep 01, 2019 at 10:07:13AM -0700, akuster808 wrote:
> 
> 
> On 9/1/19 7:05 AM, Adrian Bunk wrote:
> > thud and zeus are providing 2 gcc versions each that need fixing.
> That is a true statement. What are you expecting?

The other versions also being fixed?

gcc-8 being fixed in warrior before it gets fixed in master would be
the wrong order, and would introduce a security regression in master.

The code should be nearly identical in warrior and master, so fixing
this also in gcc-8 in master should be trivial.

Fixing gcc-7 in thud would be a bonus.

> - armin

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-09-02 12:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-31 21:15 [PATCH] gcc-9.2: Security fix for CVE-2019-14250 Armin Kuster
2019-09-01 14:05 ` Adrian Bunk
2019-09-01 17:07   ` akuster808
2019-09-02 12:40     ` Adrian Bunk [this message]
2019-09-02 16:10       ` akuster808
2019-09-02 21:33       ` akuster808
2019-09-03  3:41         ` Adrian Bunk
2019-09-03  5:50         ` Mikko.Rapeli

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=20190902124003.GA8291@localhost \
    --to=bunk@stusta.de \
    --cc=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.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