public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v1 0/5] Restore downstream mounts compatibility
Date: Wed,  7 Jul 2021 19:38:46 +0300	[thread overview]
Message-ID: <20210707163851.204296-1-amikan@ilbers.de> (raw)

Revert commit d21d49578e5a3b0019075d1946bd93a95914fcca which has broken
compatibility with upstream projects.
Make the same fix by catching bb.build.TaskFailed event and unmount
any lost paths.
Also make undo_mounts functions to be safe for calling in case there is
no do_mounts call before. This will make fail policy more tolerant.
Enable refrence counting for image mounts in case there are several
images using like ubi-ubifs-img does.

This implementation do not call buildchroot_undo_mounts in task fail
handler, because there is hard not to broke other tasks execution. So
it will not fully cover pure buildchroot_do_mounts usage like
wic-img.bbclass does.

Tested with kas-iot2050-example project from:
https://github.com/siemens/meta-iot2050

Anton Mikanovich (5):
  Revert "dpkg: Make mount buildroot reliable"
  mount: Allow calling unmount on not mounted paths
  dpkg: Remove unmount loop
  image: Add reference counter
  events: Unmount all lost mounts at task fail

 meta/classes/buildchroot.bbclass |  20 ++---
 meta/classes/dpkg-base.bbclass   | 122 +++++++++++--------------------
 meta/classes/dpkg-gbp.bbclass    |   8 +-
 meta/classes/dpkg.bbclass        |  14 +---
 meta/classes/image.bbclass       |  39 +++++++++-
 meta/classes/isar-events.bbclass |  27 +++++++
 meta/classes/rootfs.bbclass      |  20 ++---
 7 files changed, 136 insertions(+), 114 deletions(-)

-- 
2.25.1


             reply	other threads:[~2021-07-07 16:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 16:38 Anton Mikanovich [this message]
2021-07-07 16:38 ` [PATCH v1 1/5] Revert "dpkg: Make mount buildroot reliable" Anton Mikanovich
2021-07-08 12:16   ` Jan Kiszka
2021-07-07 16:38 ` [PATCH v1 2/5] mount: Allow calling unmount on not mounted paths Anton Mikanovich
2021-07-08 12:17   ` Jan Kiszka
2021-07-07 16:38 ` [PATCH v1 3/5] dpkg: Remove unmount loop Anton Mikanovich
2021-07-08 12:21   ` Jan Kiszka
2021-07-08 14:35     ` Anton Mikanovich
2021-07-08 16:16       ` Jan Kiszka
2021-08-17 13:02     ` Anton Mikanovich
2021-07-07 16:38 ` [PATCH v1 4/5] image: Add reference counter Anton Mikanovich
2021-07-07 16:38 ` [PATCH v1 5/5] events: Unmount all lost mounts at task fail Anton Mikanovich
2021-07-08 12:24   ` Jan Kiszka
2021-07-08 14:41     ` Anton Mikanovich
2021-07-08 16:28       ` Jan Kiszka
2021-07-12 16:08         ` Baurzhan Ismagulov

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=20210707163851.204296-1-amikan@ilbers.de \
    --to=amikan@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