public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: roberto.foglietta@gmail.com, isar-users@googlegroups.com
Subject: Re: [PATCH v2] rootfs class lock undefined in corner cases fix
Date: Thu, 5 Jan 2023 08:18:43 +0100	[thread overview]
Message-ID: <b4f6b5cf-af9d-e60c-c2ee-8660405ce323@siemens.com> (raw)
In-Reply-To: <20230104194646.2545099-1-roberto.foglietta@gmail.com>

On 04.01.23 20:46, roberto.foglietta@gmail.com wrote:
> From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
> 
> rootfs class lock undefined in corner cases fix
> 
> 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 = ""
>  
>          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

I thinks you didn't understand the logic yet when you are proposing such
a change and you are rather papering over a downstream issue: missing
"acquire-before" in a commend chain that later on has a "release-after".

We can improve detecting such bugs by asserting on lock being defined
when running into a "release-after".

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux


  parent reply	other threads:[~2023-01-05  7:18 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
2023-01-05  7:18 ` Jan Kiszka [this message]
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=b4f6b5cf-af9d-e60c-c2ee-8660405ce323@siemens.com \
    --to=jan.kiszka@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