From: Benjamin ROBIN <benjamin.robin@bootlin.com>
To: openembedded-core@lists.openembedded.org,
Marta Rybczynska <marta.rybczynska@syslinbit.com>,
Samantha Jalabert <samantha.jalabert@syslinbit.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Peter Marko <peter.marko@siemens.com>
Subject: Re: [PATCH 0/5] backport: allow to extract all CVE_STATUS info
Date: Thu, 20 Nov 2025 10:38:56 +0100 [thread overview]
Message-ID: <10765366.nUPlyArG6x@brobin-bootlin> (raw)
In-Reply-To: <20251120091954.211153-1-benjamin.robin@bootlin.com>
Hello,
Please ignore this serie, it is not ready, and was sent by mistake...
Really sorry.
On Thursday, November 20, 2025 at 10:19 AM, Benjamin Robin (Schneider
Electric) wrote:
> From: "Benjamin Robin" <benjamin.robin@bootlin.com>
>
> The goal of this backport is to be able to extract all CVE annotations
> provided by the CVE_STATUS and the CVE_STATUS_GROUPS variables.
>
> Currently only CVEs with "Patched" status are exported in SPDX 3.0 files.
> And CVE annotations provided by the CVE_STATUS_GROUPS variable are not
> exported, since previously this was only handled by cve-check.bbclass.
>
> Also backport the vex.bbclass, which will help users to extract all the
> information needed to do a CVE analysis outside of Yocto.
>
> With this backport, great care has been taken to avoid breaking
> compatibility. This is why the get_patched_cves() API was not changed.
> Everything that was needed is implemented in the associated .bbclass.
>
> Benjamin Robin (5):
> spdx30: provide all CVE_STATUS, not only Patched status
> vex.bbclass: add a new class
> cve-check: extract extending CVE_STATUS to library function
> spdx: extend CVE_STATUS variables
> vex: fix rootfs manifest
>
> meta/classes/cve-check.bbclass | 17 +-
> meta/classes/spdx-common.bbclass | 5 +
> meta/classes/vex.bbclass | 319 +++++++++++++++++++++++++++++++
> meta/lib/oe/cve_check.py | 22 +++
> meta/lib/oe/spdx30_tasks.py | 31 +--
> 5 files changed, 365 insertions(+), 29 deletions(-)
> create mode 100644 meta/classes/vex.bbclass
--
Benjamin Robin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
parent reply other threads:[~2025-11-20 17:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20251120091954.211153-1-benjamin.robin@bootlin.com>]
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=10765366.nUPlyArG6x@brobin-bootlin \
--to=benjamin.robin@bootlin.com \
--cc=marta.rybczynska@syslinbit.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=samantha.jalabert@syslinbit.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