public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: simone.p.weiss@posteo.com
To: openembedded-core@lists.openembedded.org
Cc: "Simone Weiß" <simone.p.weiss@posteo.com>
Subject: [PATCH] cve-check: Log if CVE_STATUS set but not reported for component
Date: Fri, 23 Feb 2024 21:08:48 +0000	[thread overview]
Message-ID: <20240223210848.21731-1-simone.p.weiss@posteo.com> (raw)

From: Simone Weiß <simone.p.weiss@posteo.com>

Log if the CVE_STATUS is set for a CVE, but the cve is not reported for a
component. This should hopefully help to clean up not needed CVE_STATUS
settings. 

Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com>
---
 meta/classes/cve-check.bbclass | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 5191d04303..b82a9e89ec 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -418,6 +418,9 @@ def check_cves(d, patched_cves):
             cves_status.append([product, False])
 
     conn.close()
+    diff_ignore = list(set(cve_ignore) - set(cves_ignored))
+    if diff_ignore:
+        bb.warn("Found CVE (%s) with CVE_STATUS set that is not found in database for this component" % " ".join(diff_ignore))
 
     if not cves_in_recipe:
         bb.note("No CVE records for products in recipe %s" % (pn))
-- 
2.39.2



             reply	other threads:[~2024-02-23 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 21:08 simone.p.weiss [this message]
2024-02-23 21:52 ` [OE-core] [PATCH] cve-check: Log if CVE_STATUS set but not reported for component Yoann CONGAL
2024-02-24  0:01   ` Simone Weiß
2024-02-24 14:28 ` Marko, Peter
2024-02-24 15:41   ` Simone Weiß
2024-02-24 15:53   ` Richard Purdie

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=20240223210848.21731-1-simone.p.weiss@posteo.com \
    --to=simone.p.weiss@posteo.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