From: Henning Schild <henning.schild@siemens.com>
To: roberto.foglietta@gmail.com
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2] rootfs class lock undefined in corner cases fix
Date: Wed, 4 Jan 2023 21:31:03 +0100 [thread overview]
Message-ID: <20230104213103.13ec20d5@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20230104194646.2545099-1-roberto.foglietta@gmail.com>
Am Wed, 4 Jan 2023 20:46:46 +0100
schrieb roberto.foglietta@gmail.com:
> From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
>
> rootfs class lock undefined in corner cases fix
Could you go into details of what those corner cases are?
We would obviously all assume that your base is Isar next, in case we
are talking about a fork already on bb2 that might all be a reply to
the bb2 series, or a patch based on top.
> Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
> ---
> meta/classes/rootfs.bbclass | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
> index b3faade..63735d4 100644
> --- a/meta/classes/rootfs.bbclass
> +++ b/meta/classes/rootfs.bbclass
> @@ -198,11 +198,14 @@ python do_rootfs_install() {
> if (d.getVarFlag(cmd, 'isar-apt-lock') or "") ==
> "acquire-before": lock = bb.utils.lockfile(d.getVar("REPO_ISAR_DIR")
> + "/isar.lock", shared=True)
> + else:
> + lock = ""
if we fail to grab that lock for any reason ... are you sure we can
keep going and release the lock only when we got it?
There must be some reason for the lock and not getting it likely means
we should not continue ignoring the problem.
Maybe we rather have to keep looping and trying until we get that lock.
Henning
>
> bb.build.exec_func(cmd, d)
>
> if (d.getVarFlag(cmd, 'isar-apt-lock') or "") ==
> "release-after":
> - bb.utils.unlockfile(lock)
> + if (lock != ""):
> + bb.utils.unlockfile(lock)
> progress_reporter.finish()
> }
> addtask rootfs_install before do_rootfs_postprocess after do_unpack
next prev parent reply other threads:[~2023-01-04 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 19:46 roberto.foglietta
2023-01-04 20:31 ` Henning Schild [this message]
2023-01-05 7:18 ` Jan Kiszka
2023-01-05 17:32 ` Roberto A. Foglietta
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=20230104213103.13ec20d5@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@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