From: Quentin Schulz <quentin.schulz@cherry.de>
To: Daniel Turull <daniel.turull@ericsson.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Cc: Joshua Watt <JPEWhacker@gmail.com>,
Peter Marko <peter.marko@siemens.com>
Subject: Re: [OE-core] [PATCH v4 1/3] spdx: add option to include only compiled sources
Date: Thu, 15 May 2025 15:32:53 +0200 [thread overview]
Message-ID: <50889349-4a1c-4978-a4e2-b7bf1964b881@cherry.de> (raw)
In-Reply-To: <PR3PR07MB666678F2C4E5BA67075D490D8A90A@PR3PR07MB6666.eurprd07.prod.outlook.com>
Hi Daniel,
On 5/15/25 3:12 PM, Daniel Turull wrote:
> Hi Quentin,
> Thanks for the feedback. That's a good point for the header files and the rust files. I'll need to find a better way to extract them, since scripts/clang-tools/gen_compile_commands.py only extracts the commands and includes only the c files. So unless we don't have better info on the files used, we should not exclude any header file. Do you
I would then suggest to include all files by default and only exclude C
files if they do not appear in the output of
scripts/clang-tools/gen_compile_commands.py so you cover everything and
allowlist only things you know are safe.
know any better script to extract the compiled files from the kernel?
>
No clue, sorry.
> The current code in the spdx class is supposed to only ignore the c files that are not compiled, (so been conservative on what to remove) but probably the script that I have in [PATCH v4 3/3] improve_kernel_cve_report: add script for postprocesing of kernel CVE data.
>
> Needs to be updated, that if the CVE is not in a c file is not ignored, unless we have the header files in the list of compiled files.
>
Anything that is NOT a C file should NOT be ignored (except if you have
a tool that allows to know which non-C files are compiled in). Anything
you can guarantee is never compiled in, then you can ignore. For now it
seems you're saying gen_compile_commands.py only returns C files so
that's all we can filter out.
Cheers,
Quentin
next prev parent reply other threads:[~2025-05-15 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 12:57 [PATCH v4 0/3] Check compiled files to filter kernel CVEs daniel.turull
2025-05-14 12:57 ` [PATCH v4 1/3] spdx: add option to include only compiled sources daniel.turull
2025-05-15 12:10 ` [OE-core] " Quentin Schulz
2025-05-15 13:12 ` Daniel Turull
2025-05-15 13:32 ` Quentin Schulz [this message]
2025-05-15 13:44 ` Daniel Turull
2025-05-15 13:58 ` Quentin Schulz
2025-05-15 14:04 ` Daniel Turull
2025-05-15 14:03 ` Richard Purdie
2025-05-15 14:09 ` Daniel Turull
2025-05-15 14:21 ` Richard Purdie
2025-05-15 14:24 ` Daniel Turull
2025-05-14 12:57 ` [PATCH v4 2/3] kernel: add support to extract compiled files daniel.turull
2025-05-14 12:57 ` [PATCH v4 3/3] improve_kernel_cve_report: add script for postprocesing of kernel CVE data daniel.turull
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=50889349-4a1c-4978-a4e2-b7bf1964b881@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=JPEWhacker@gmail.com \
--cc=daniel.turull@ericsson.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.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