Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <stondo@gmail.com>, <openembedded-core@lists.openembedded.org>
Cc: "Joshua Watt" <JPEWhacker@gmail.com>,
	"Alexander Kanavin" <alex.kanavin@gmail.com>,
	"Stefan Herbrechtsmeier" <stefan.herbrechtsmeier@weidmueller.com>,
	"Stefano Tondo" <stefano.tondo.ext@siemens.com>
Subject: Re: [OE-core] [PATCH 3/4] spdx30: Add the PURLs of the source downloads to the output packages
Date: Wed, 18 Nov 2026 16:22:10 +0100	[thread overview]
Message-ID: <DMYFTUY2A6RH.1WI2PDCNCPOJY@bootlin.com> (raw)
In-Reply-To: <20261118092927.204959-4-stondo@gmail.com>

On Wed Nov 18, 2026 at 10:29 AM CET, Stefano Tondo via openembedded-core wrote:
> From: Stefano Tondo <stefano.tondo.ext@siemens.com>
>
> Statically linked code, for example a Rust crate, is part of the
> binary, but the SPDX of the output package only names the recipe.
> A vulnerability scanner that checks the packages of an image does
> not find the dependency.
>
> Add the PURLs of the source downloads to the external identifiers of
> each output package. Leave out the crates that the cargo dependency
> graph proves are not built into the target. The software_packageUrl
> of the package stays the first PURL in SPDX_PACKAGE_URLS.
>
> Signed-off-by: Stefano Tondo <stefano.tondo.ext@siemens.com>
> ---

Hi Stefano,

Thanks for your patches.

It looks like this is using memory in a way it got killed several times
on the autobuilder. Locally, I managed to have a do_create_spdx task
using more than 10GB of memory, with a value continuously increasing of
about 100MB/s.

This can be reproduced with master branch + your patches, then:
bitbake python3-uv-build-native -c do_create_spdx

Some failed builds for reference:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/110/builds/1605
https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/5058
https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/5060
https://autobuilder.yoctoproject.org/valkyrie/#/builders/25/builds/5039
https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/5061

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2026-11-18 15:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18  9:29 [PATCH 0/4] spdx30: identity and purls of dependency downloads Stefano Tondo
2026-11-18  9:29 ` [PATCH 1/4] spdx30: Take name, version and PURL of downloads from the fetcher Stefano Tondo
2026-11-18  9:29 ` [PATCH 2/4] spdx30: Record the lifecycle scope of crate dependencies Stefano Tondo
2026-11-18  9:29 ` [PATCH 3/4] spdx30: Add the PURLs of the source downloads to the output packages Stefano Tondo
2026-11-18 15:22   ` Mathieu Dubois-Briand [this message]
2026-11-18 23:44     ` Stefano Tondo
2026-11-18  9:29 ` [PATCH 4/4] oeqa/selftest: spdx: Test crate identity, scope and output PURLs Stefano Tondo

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=DMYFTUY2A6RH.1WI2PDCNCPOJY@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=JPEWhacker@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=stefan.herbrechtsmeier@weidmueller.com \
    --cc=stefano.tondo.ext@siemens.com \
    --cc=stondo@gmail.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