public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/1] isar-apt: fix race-condition in do_cache_config
Date: Wed, 3 Jun 2026 11:56:41 +0000	[thread overview]
Message-ID: <637973be3794202fa627f6026e8a826275d68670.camel@siemens.com> (raw)
In-Reply-To: <20260603114618.3291059-1-felix.moessbauer@siemens.com>

On Wed, 2026-06-03 at 13:46 +0200, Felix Moessbauer wrote:
> Repo configuration operations on the isar apt have to happen while
> holding the isar lock. However, bitbake executes the cleandirs operation
> without holding the lock, introducing a race-condition that sporadically
> breaks the build with the following error:
> 
>   Error opening config file '/isar/build/tmp/deploy/isar-apt/
>   debian-trixie/apt/debian-trixie/conf/distributions': No such file
>   or directory(2)
> 
> We fix this by open-coding the cleandirs logic inside the function and
> by that under the lock.
> 
> Fixes: be290896 ("isar-apt: support further optional fields ...")

PS: Commit "Revert "Split up isar-apt into distro-arch specific
instances" probably made it much more likely to run into the race-
condition, but the race was there before.

Felix

-- 
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/637973be3794202fa627f6026e8a826275d68670.camel%40siemens.com.

  reply	other threads:[~2026-06-03 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 11:46 'Felix Moessbauer' via isar-users
2026-06-03 11:56 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-06-04  9:39   ` Anton Mikanovich
2026-06-05 14:22     ` Anton Mikanovich
2026-06-05 14:24 ` Anton Mikanovich

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=637973be3794202fa627f6026e8a826275d68670.camel@siemens.com \
    --to=isar-users@googlegroups.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