From: Mike Crowe <mac@mcrowe.com>
To: Steve Sakoman <steve@sakoman.com>
Cc: Ralph Siemsen <ralph.siemsen@linaro.org>,
Ross Burton <ross@burtonini.com>,
"Mittal, Anuj" <anuj.mittal@intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH][dunfell] zlib: backport the fix for CVE-2018-25032
Date: Wed, 13 Apr 2022 17:41:42 +0100 [thread overview]
Message-ID: <Ylb9RoAyRpDHTaqe@mcrowe.com> (raw)
In-Reply-To: <CAOSpxdYONLK8BhmNjx9uj9BDb0P=bAiJ-uAKG1edHjBnzvHc9g@mail.gmail.com>
On Wednesday 13 April 2022 at 06:02:22 -1000, Steve Sakoman wrote:
> Both runs completed and I'm still seeing success without the zlib patch:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/5069
>
> and failure with the patch:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/5070
I'm certainly no expert with the autobuilder, but it looks like nothing was
actually compiled for both of those builds - everything came from the
sstate cache.
I believe that Ralph's reproduction of the test failure without the zlib
patch was from a complete rebuild without anything coming from the sstate
cache.
I suspect that if a PR bump or something similar that causes zlib and all
its reverse dependencies to be built were tested on top of the commit used
for build 5069 then the test failure would occur then as well and
exonerate the zlib patch.
Mike.
next prev parent reply other threads:[~2022-04-14 16:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 13:07 [PATCH][dunfell] zlib: backport the fix for CVE-2018-25032 Ross Burton
2022-03-29 19:49 ` [OE-core] " Steve Sakoman
2022-03-30 20:40 ` Ross Burton
2022-03-30 22:57 ` Steve Sakoman
2022-04-04 15:22 ` Steve Sakoman
2022-04-11 17:31 ` Ralph Siemsen
2022-04-11 17:52 ` Steve Sakoman
2022-04-11 18:17 ` Ralph Siemsen
2022-04-11 18:58 ` Steve Sakoman
2022-04-11 22:30 ` Ralph Siemsen
2022-04-11 22:42 ` Steve Sakoman
2022-04-12 1:33 ` Ralph Siemsen
2022-04-12 2:12 ` Steve Sakoman
2022-04-12 16:07 ` Ralph Siemsen
2022-04-12 21:49 ` Steve Sakoman
2022-04-13 1:21 ` Ralph Siemsen
2022-04-13 15:31 ` Steve Sakoman
[not found] ` <16E57E79FD292EFA.13992@lists.openembedded.org>
2022-04-13 16:02 ` Steve Sakoman
2022-04-13 16:41 ` Mike Crowe [this message]
2022-04-13 17:37 ` Steve Sakoman
2022-04-13 17:50 ` Jose Quaresma
2022-04-13 19:16 ` Steve Sakoman
2022-04-13 18:02 ` Ralph Siemsen
2022-04-13 18:19 ` Steve Sakoman
2022-04-13 19:05 ` Ralph Siemsen
2022-04-13 21:39 ` Steve Sakoman
2022-04-13 21:41 ` Richard Purdie
2022-04-13 21:44 ` Steve Sakoman
2022-04-14 2:47 ` Ralph Siemsen
2022-04-14 3:00 ` Steve Sakoman
[not found] ` <16E5A41A6E4FF34A.8845@lists.openembedded.org>
2022-04-14 3:02 ` Steve Sakoman
2022-04-14 3:03 ` Steve Sakoman
2022-04-13 17:11 ` Jose Quaresma
[not found] ` <16E583EB139C493B.16998@lists.openembedded.org>
2022-04-13 17:41 ` Jose Quaresma
2022-03-31 0:24 ` Mittal, Anuj
2022-04-05 19:04 ` Jeroen Hofstee
2022-04-09 18:14 ` Steve Sakoman
2022-04-10 21:21 ` Jeroen Hofstee
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=Ylb9RoAyRpDHTaqe@mcrowe.com \
--to=mac@mcrowe.com \
--cc=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ralph.siemsen@linaro.org \
--cc=ross@burtonini.com \
--cc=steve@sakoman.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