From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v2 0/5] isar: Rebuild mount logic
Date: Wed, 21 Apr 2021 17:58:50 +0300 [thread overview]
Message-ID: <20210421145855.66257-1-amikan@ilbers.de> (raw)
Mounting is perfomed very inconsistent currently in Isar. A lot of mount
points are left after task execution and stays mounted until cleanup in
build_completed hook.
We already experienced issues with stuck forever on unmounting at
"Couldn't unmount, retrying..." error.
It is also quite easy to face with a lot of ramaining mounts after the
failed or interrupted manual builds.
This patchset implements unmounting paths after usage. In the cases of
mount sharing corresponding request counting is performed, so real mount
will be done only at first request, real unmount will be done only after
the last task will try to unmount the path.
Meantime build_completed will use emergency only, so following warning
added to show something goes wrong.
---
Changes since v1:
- Make all mounts be unmounted after use.
- Warn about lost mounts after finish.
Known issues:
- Full CI fails for qemuarm64-stretch.
Anton Mikanovich (5):
dpkg: Make mount buildroot reliable
buildchroot: Unmount buildchroot if not needed
rootfs: Unmount rootfs mounts if not needed
wic: Unmount dirs after usage
events: Warn if mounted paths left
meta/classes/buildchroot.bbclass | 58 ++++++++
meta/classes/dpkg-base.bbclass | 127 +++++++++++-------
meta/classes/dpkg-gbp.bbclass | 8 +-
meta/classes/dpkg.bbclass | 14 +-
meta/classes/ext4-img.bbclass | 2 +
meta/classes/fit-img.bbclass | 2 +
meta/classes/image-tools-extension.bbclass | 2 +
meta/classes/image.bbclass | 24 ++--
meta/classes/initramfs.bbclass | 2 +
meta/classes/isar-events.bbclass | 2 +
meta/classes/rootfs.bbclass | 68 +++++++++-
meta/classes/ubi-img.bbclass | 2 +
meta/classes/ubifs-img.bbclass | 2 +
meta/classes/wic-img.bbclass | 10 ++
.../buildchroot/buildchroot.inc | 7 +
15 files changed, 249 insertions(+), 81 deletions(-)
--
2.25.1
next reply other threads:[~2021-04-21 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 14:58 Anton Mikanovich [this message]
2021-04-21 14:58 ` [PATCH v2 1/5] dpkg: Make mount buildroot reliable Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 2/5] buildchroot: Unmount buildchroot if not needed Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 3/5] rootfs: Unmount rootfs mounts " Anton Mikanovich
2021-08-12 5:39 ` Jan Kiszka
2021-08-12 9:09 ` Anton Mikanovich
2021-08-12 9:25 ` Jan Kiszka
2021-08-13 16:27 ` Anton Mikanovich
2021-08-15 19:05 ` Jan Kiszka
2021-04-21 14:58 ` [PATCH v2 4/5] wic: Unmount dirs after usage Anton Mikanovich
2021-04-21 14:58 ` [PATCH v2 5/5] events: Warn if mounted paths left 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=20210421145855.66257-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