public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/3] Fix data-race in deployment of initrd
Date: Mon, 06 Mar 2023 09:05:06 +0300	[thread overview]
Message-ID: <4760936.OV4Wx5bFTl@home> (raw)
In-Reply-To: <20230223064359.4171845-1-felix.moessbauer@siemens.com>

In the email from Thursday, 23 February 2023 09:43:56 +03 user Felix Moessbauer wrote:
> Changes since v2:
> 
> - fix check for default initrd
> 
> Changes since v1:
> 
> - add API changelog entry
> - fix expression in INITRD_DEPLOY_FILE
> - do not append ${PN} to deploy-dir in image.bb
> 
> This patch fixes a data race in the deployment of the initrd, as discussed on
> the ML in "Issues creating images with custom initramfs". As a measure against
> further races on these files, we also use the sstate cache for deployment.
> 
> Please note, that imaging with wic + grub or systemd-boot with a custom
> initramfs is still broken. This is due to the wic logic, which reads the
> initrd in the rootfs, but not the one in the deploy dir.
> 
> Best regards,
> Felix Moessbauer
> Siemens AG
> 
> Felix Moessbauer (3):
>   add initramfs to sstate-cache
>   deploy boot files via sstate-cache
>   fix race-cond between default and custom initrd
> 
>  RECIPE-API-CHANGELOG.md        |  8 ++++++++
>  meta/classes/image.bbclass     | 36 ++++++++++++++++++++++------------
>  meta/classes/initramfs.bbclass | 18 ++++++++++++-----
>  scripts/start_vm               |  4 ++--
>  testsuite/start_vm.py          |  2 +-
>  5 files changed, 48 insertions(+), 20 deletions(-)
> 
> 

Applied (with removing redundant expand=True in patch 3) to next, thanks.




      parent reply	other threads:[~2023-03-06  6:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23  6:43 Felix Moessbauer
2023-02-23  6:43 ` [PATCH v3 1/3] add initramfs to sstate-cache Felix Moessbauer
2023-02-23  6:43 ` [PATCH v3 2/3] deploy boot files via sstate-cache Felix Moessbauer
2023-12-29  7:29   ` Anton Mikanovich
2024-01-09 12:46     ` MOESSBAUER, Felix
2024-01-09 13:46       ` Jan Kiszka
2024-01-09 14:04         ` Anton Mikanovich
2024-01-10  4:27           ` Jan Kiszka
2024-02-26 13:32             ` Uladzimir Bely
2024-02-26 18:17               ` MOESSBAUER, Felix
2023-02-23  6:43 ` [PATCH v3 3/3] fix race-cond between default and custom initrd Felix Moessbauer
2023-03-06  6:05 ` Uladzimir Bely [this message]

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=4760936.OV4Wx5bFTl@home \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.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