From: Greg KH <gregkh@linuxfoundation.org>
To: Luis Augenstein <luis.augenstein@tngtech.com>
Cc: nathan@kernel.org, nsc@kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
maximilian.huber@tngtech.com
Subject: Re: [PATCH 00/14] Add SPDX SBOM generation tool
Date: Mon, 19 Jan 2026 10:51:29 +0100 [thread overview]
Message-ID: <2026011916-idealism-paternal-cfd5@gregkh> (raw)
In-Reply-To: <20260119064731.23879-1-luis.augenstein@tngtech.com>
On Mon, Jan 19, 2026 at 07:47:17AM +0100, Luis Augenstein wrote:
> This patch series introduces a Python-based tool for generating SBOM
> documents in the SPDX 3.0.1 format for kernel builds.
>
> A Software Bill of Materials (SBOM) describes the individual components
> of a software product. For the kernel, the goal is to describe the
> distributable build outputs (typically the kernel image and modules),
> the source files involved in producing these outputs, and the build
> process that connects the source and output files.
>
> To achieve this, the SBOM tool generates three SPDX documents:
>
> - sbom-output.spdx.json
> Describes the final build outputs together with high-level
> build metadata.
>
> - sbom-source.spdx.json
> Describes all source files involved in the build, including
> licensing information and additional file metadata.
>
> - sbom-build.spdx.json
> Describes the entire build process, linking source files
> from the source SBOM to output files in the output SBOM.
>
> The sbom tool is optional and runs only when CONFIG_SBOM is enabled. It
> is invoked after the build, once all output artifacts have been
> generated. Starting from the kernel image and modules as root nodes,
> the tool reconstructs the dependency graph up to the original source
> files. Build dependencies are primarily derived from the .cmd files
> generated by Kbuild, which record the full command used to build
> each output file.
>
> Currently, the tool only supports x86 and arm64 architectures.
>
> Co-developed-by: Maximilian Huber <maximilian.huber@tngtech.com>
> Signed-off-by: Maximilian Huber <maximilian.huber@tngtech.com>
> Signed-off-by: Luis Augenstein <luis.augenstein@tngtech.com>
This is great work, thank you so much for doing this!
Note, I just tested the series, on 6.19-rc6, and with CONFIG_SBOM
enabled, I get this following "message" at the end of the build when it
generates the sbom:
make[3]: Nothing to be done for 'sbom'.
Is that intentional?
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-19 9:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 6:47 [PATCH 00/14] Add SPDX SBOM generation tool Luis Augenstein
2026-01-19 6:47 ` [PATCH 01/14] tools/sbom: integrate tool in make process Luis Augenstein
2026-01-19 6:47 ` [PATCH 02/14] tools/sbom: setup sbom logging Luis Augenstein
2026-01-19 6:47 ` [PATCH 03/14] tools/sbom: add command parsers Luis Augenstein
2026-01-19 6:47 ` [PATCH 04/14] tools/sbom: add cmd graph generation Luis Augenstein
2026-01-19 6:47 ` [PATCH 05/14] tools/sbom: add additional dependency sources for cmd graph Luis Augenstein
2026-01-19 6:47 ` [PATCH 06/14] tools/sbom: add SPDX classes Luis Augenstein
2026-01-19 6:47 ` [PATCH 07/14] tools/sbom: add JSON-LD serialization Luis Augenstein
2026-01-19 6:47 ` [PATCH 08/14] tools/sbom: add shared SPDX elements Luis Augenstein
2026-01-19 6:47 ` [PATCH 09/14] tools/sbom: collect file metadata Luis Augenstein
2026-01-19 6:47 ` [PATCH 10/14] tools/sbom: add SPDX output graph Luis Augenstein
2026-01-19 6:47 ` [PATCH 11/14] tools/sbom: add SPDX source graph Luis Augenstein
2026-01-19 6:47 ` [PATCH 12/14] tools/sbom: add SPDX build graph Luis Augenstein
2026-01-19 6:47 ` [PATCH 13/14] tools/sbom: add unit tests for command parsers Luis Augenstein
2026-01-19 6:47 ` [PATCH 14/14] tools/sbom: Add unit tests for SPDX-License-Identifier parsing Luis Augenstein
2026-01-19 9:51 ` Greg KH [this message]
2026-01-19 10:00 ` [PATCH 00/14] Add SPDX SBOM generation tool Greg KH
2026-01-19 20:08 ` Luis Augenstein
2026-01-20 6:08 ` Greg KH
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=2026011916-idealism-paternal-cfd5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.augenstein@tngtech.com \
--cc=maximilian.huber@tngtech.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.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