From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: adriaan.schmidt@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 0/2] Fix data races in sstate tasks
Date: Thu, 25 Jun 2026 17:02:30 +0200 [thread overview]
Message-ID: <20260625150232.531442-1-felix.moessbauer@siemens.com> (raw)
While extensively testing the rootless builds in a CI running with
sstate cache, I was finally able to pin-point some sporadic issues.
These issues are completely unrelated to the rootless builds, though.
They have been around for quite some time, but were quite unlikely
to hit on normal (non multiconfig) builds.
Best regards,
Felix Moessbauer
Felix Moessbauer (2):
fix(rootfs): protect rootfs_install sstate prepare with lock
sstate: guard sstate funcs against execution in wrong context
meta/classes-recipe/dpkg-base.bbclass | 4 ++++
meta/classes-recipe/rootfs.bbclass | 6 +++++-
meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc | 4 ++++
3 files changed, 13 insertions(+), 1 deletion(-)
--
2.53.0
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/20260625150232.531442-1-felix.moessbauer%40siemens.com.
next reply other threads:[~2026-06-25 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 15:02 'Felix Moessbauer' via isar-users [this message]
2026-06-25 15:02 ` [PATCH 1/2] fix(rootfs): protect rootfs_install sstate prepare with lock 'Felix Moessbauer' via isar-users
2026-06-25 15:02 ` [PATCH 2/2] sstate: guard sstate funcs against execution in wrong context 'Felix Moessbauer' via isar-users
2026-06-25 16:43 ` 'Jan Kiszka' via isar-users
2026-06-25 22:16 ` 'MOESSBAUER, Felix' via isar-users
2026-07-01 9:06 ` [PATCH 0/2] Fix data races in sstate tasks Zhihang Wei
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=20260625150232.531442-1-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@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