From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: JPEWhacker@gmail.com
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
OE-core <openembedded-core@lists.openembedded.org>,
Ross Burton <ross.burton@arm.com>
Subject: Re: [OE-core][PATCH] lib: spdx30_tasks: Handle patched CVEs
Date: Tue, 11 Mar 2025 15:46:27 +0200 [thread overview]
Message-ID: <Z9A-s_NNJl_Cw3sf@nuoska> (raw)
In-Reply-To: <CAJdd5GY=pQ85g4M6gYHq2y7JKTT4BK+A2mi8dTJ6APnapvuozA@mail.gmail.com>
Hi,
On Tue, Mar 11, 2025 at 07:17:33AM -0600, Joshua Watt via lists.openembedded.org wrote:
> On Tue, Mar 11, 2025, 7:01 AM Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
>
> > On Thu, 2025-03-06 at 14:20 -0700, Joshua Watt via
> > lists.openembedded.org wrote:
> > > The code to iterate over patched CVEs (e.g. those patched by a .patch
> > > file in SRC_URI) was accidentally omitted when writing the SPDX 3
> > > handling. Add it in now
> > >
> > > [YOCTO #15789]
> > >
> > > Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> > > ---
> > > meta/lib/oe/spdx30_tasks.py | 10 ++++++++++
> > > 1 file changed, 10 insertions(+)
> > >
> > > diff --git a/meta/lib/oe/spdx30_tasks.py
> > > b/meta/lib/oe/spdx30_tasks.py
> > > index e3e5dbc7427..e20bb0c86f3 100644
> > > --- a/meta/lib/oe/spdx30_tasks.py
> > > +++ b/meta/lib/oe/spdx30_tasks.py
> > > @@ -498,6 +498,16 @@ def create_spdx(d):
> > > # Add CVEs
> > > cve_by_status = {}
> > > if include_vex != "none":
> > > + for cve in oe.cve_check.get_patched_cves(d):
> > > + spdx_cve = build_objset.new_cve_vuln(cve)
> > > + build_objset.set_element_alias(spdx_cve)
> > > +
> > > + cve_by_status.setdefault("Patched", {})[cve] = (
> > > + spdx_cve,
> > > + "patched",
> > > + "",
> > > + )
> > > +
> > > for cve in d.getVarFlags("CVE_STATUS") or {}:
> > > decoded_status = oe.cve_check.decode_cve_status(d, cve)
> > >
> >
> > I worry this has increased the build time by around 10 mins (~25%):
> >
> >
> > https://valkyrie.yocto.io/pub/non-release/20250311-54/testresults/buildperf-alma8/perf-alma8-vk_master_20250311090119_046a92d351.html
>
>
> Ok. Let me see what I can do about that
Yes please. I think the kernel build time increase from ~4 minutes to ~16 minutes is
what I saw in my local builds. Both kernel and image builds are affected by these
SDPX CVE data changes, as we discussed yesterday on #yocto irc.
Cheers,
-Mikko
prev parent reply other threads:[~2025-03-11 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 21:20 [OE-core][PATCH] lib: spdx30_tasks: Handle patched CVEs Joshua Watt
2025-03-11 13:01 ` Richard Purdie
2025-03-11 13:17 ` Joshua Watt
2025-03-11 13:46 ` Mikko Rapeli [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=Z9A-s_NNJl_Cw3sf@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=JPEWhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.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 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.