From: ValentinBoudevin <valentin.boudevin@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: ValentinBoudevin <valentin.boudevin@gmail.com>
Subject: [PATCH v3 0/4] generate-cve-exclusions: Add a new bbclass
Date: Tue, 6 Jan 2026 15:46:42 -0500 [thread overview]
Message-ID: <20260106204646.3417382-1-valentin.boudevin@gmail.com> (raw)
Use the script generate-cve-exclusions.py in a class to generate kernel CVE
exclusion from cvelistV5 and integrates it into linux-yocto.
Changes since v2:
- Patch 4/4: Inherit the new bbclass in linux-yocto.inc instead of
individual recipes.
Changes since v1:
- Patch 2/4: Removed the mandatory execution of the
generate-cve-exclusions class on every build. It now needs to be
manually run using:
bitbake -c generate-cve-exclusions <kernel-recipe>
ValentinBoudevin (4):
generate-cve-exclusions: Add --output-json option
generate-cve-exclusions: Add a .bbclass
generate-cve-exclusions: Move python script
linux: Add inherit on generate-cve-exclusions
meta/classes/generate-cve-exclusions.bbclass | 67 +++++++++++++++++++
meta/recipes-kernel/linux/linux-yocto.inc | 3 +
.../contrib}/generate-cve-exclusions.py | 64 ++++++++++++++----
3 files changed, 120 insertions(+), 14 deletions(-)
create mode 100644 meta/classes/generate-cve-exclusions.bbclass
rename {meta/recipes-kernel/linux => scripts/contrib}/generate-cve-exclusions.py (71%)
next reply other threads:[~2026-01-06 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 20:46 ValentinBoudevin [this message]
2026-01-06 20:46 ` [PATCH v3 1/4] generate-cve-exclusions: Add --output-json option ValentinBoudevin
2026-01-06 20:46 ` [PATCH v3 2/4] generate-cve-exclusions: Add a .bbclass ValentinBoudevin
2026-01-08 8:28 ` [OE-core] " Daniel Turull
2026-01-06 20:46 ` [PATCH v3 3/4] generate-cve-exclusions: Move python script ValentinBoudevin
2026-01-06 20:46 ` [PATCH v3 4/4] linux: Add inherit on generate-cve-exclusions ValentinBoudevin
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=20260106204646.3417382-1-valentin.boudevin@gmail.com \
--to=valentin.boudevin@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