From: Ross Burton <Ross.Burton@arm.com>
To: "akash.hadke@kpit.com" <akash.hadke@kpit.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [poky][master][kirkstone][PATCH] cve-check.bbclass: Add anonymous function to get patched CVEs from recipe
Date: Mon, 18 Jul 2022 15:16:01 +0000 [thread overview]
Message-ID: <AAE95E75-469F-4C53-8922-CE8FD80701CD@arm.com> (raw)
In-Reply-To: <15370.1657624891584790233@lists.openembedded.org>
On 12 Jul 2022, at 12:21, akash hadke via lists.openembedded.org <akash.hadke=kpit.com@lists.openembedded.org> wrote:
> We can inherit cve-check by default in the configuration to export CVE information like CVE_PRODUCT, CVE_VERSION and the newly added variable CVE_PATCHED. And CVE_CHECK_WITH_DB variable will avoid scanning the CVEs from DB
> It will work like 2 operational mode for cve-check.bbclass
Looking more closely, that’s going to be a pretty horrible performance hit because you’re scanning the entire sources tree every time the recipe is parsed.
If you have CVE_CHECK_WITH_DB, why do you need this variable at all?
Ross
next prev parent reply other threads:[~2022-07-18 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 10:27 [poky][master][kirkstone][PATCH] cve-check.bbclass: Add anonymous function to get patched CVEs from recipe Akash Hadke
2022-07-12 11:00 ` [OE-core] " Ross Burton
2022-07-12 11:21 ` akash hadke
2022-07-18 15:16 ` Ross Burton [this message]
2022-07-19 7:54 ` akash hadke
2022-07-20 11:41 ` [OE-core] " Ross Burton
2022-07-21 10:37 ` akash hadke
2022-07-19 18:49 ` [OE-core] " Marta Rybczynska
2022-07-20 7:47 ` akash hadke
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=AAE95E75-469F-4C53-8922-CE8FD80701CD@arm.com \
--to=ross.burton@arm.com \
--cc=akash.hadke@kpit.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