Repository navigation
why: tell whether a CVE is covered, and if not, why - #212
Merged
Merged
Conversation
Each run writes cves.json: the status of each CVE per series. `fasttrack why <CVE>` reads it with the CVE record. A CVE from another CNA gets "not a Linux kernel CVE". report.md and cves.json use one classification, so they agree. Signed-off-by: Igor Pecovnik <igor@armbian.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Goal: one command answers "do we cover CVE-X, and if not, why".
cves.json: status per CVE and series, with reason and patch file. The workflow commits it.whyneeds nosync. Without a local feed, it reads the record from CVE.org.report.mdandcves.jsonuse one classification.report.mdoutput is unchanged (byte-identical on a 6.1 + 6.18 run).Tests: unit tests pass; a new test covers
why.