From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>
Subject: [PATCH v3 0/8] Hanging mount fixes
Date: Fri, 11 Oct 2024 13:00:42 +0300 [thread overview]
Message-ID: <20241011100050.322686-1-amikan@ilbers.de> (raw)
Consolidate the patches to address the hanging mount issues.
Addresses the following issues:
1. Cleanup handler is called multiple times, unmounting any hanging
mounts.
2. Hanging mount warnings are discarded in the current setup.
3. Incorrect asymmetric mount-umount logic inherited from buildchroot
times.
In this series, cleanup is done in reverse /proc/mounts order to
unmount e.g. /dev/shm before /dev. This happens to work for us today
but we could perform stricter semantic ordering if necessary.
ISAR_FAIL_ON_CLEANUP=1 can be set in the environment to fail builds if
mounts are left behind. We will use this for Isar CI. The default is 0.
p1 comes from 'Additional CI improvements' series.
Patches p4-p6 come from v2 of 'Start to address umount problems' series
by Jan.
p7 comes from 'Fix leftover mounts in rootfs.bbclass' by Florian.
p2, p3 and p8 are new one.
Anton Mikanovich (4):
CI: Do not lose output on bitbake / qemu exit
isar-events: Unhide mounts left behind
CI: Pass ISAR_FAIL_ON_CLEANUP from environment to bitbake
image: Do not call rootfs_do_umounts twice
Florian Bezdeka (1):
rootfs: Add missing umounts in rootfs_postprocess() and
rootfs_install()
Jan Kiszka (3):
image: Avoid breaking the build when mounts are no longer present on
umount
rootfs: Provide rootfs_do_umounts
initramfs: Add missing umounts after generation
RECIPE-API-CHANGELOG.md | 15 ++++++++
meta/classes/image.bbclass | 19 ----------
meta/classes/initramfs.bbclass | 2 +
meta/classes/isar-events.bbclass | 40 ++++++++++++++++----
meta/classes/rootfs.bbclass | 63 ++++++++++++++++++++++++++------
testsuite/cibuilder.py | 13 +++++--
6 files changed, 110 insertions(+), 42 deletions(-)
--
2.34.1
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/20241011100050.322686-1-amikan%40ilbers.de.
next reply other threads:[~2024-10-11 10:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 10:00 Anton Mikanovich [this message]
2024-10-11 10:00 ` [PATCH v3 1/8] CI: Do not lose output on bitbake / qemu exit Anton Mikanovich
2024-10-11 10:00 ` [PATCH v3 2/8] isar-events: Unhide mounts left behind Anton Mikanovich
2024-10-11 10:00 ` [PATCH v3 3/8] CI: Pass ISAR_FAIL_ON_CLEANUP from environment to bitbake Anton Mikanovich
2024-10-11 10:00 ` [PATCH v3 4/8] image: Avoid breaking the build when mounts are no longer present on umount Anton Mikanovich
2024-10-11 10:00 ` [PATCH v3 5/8] rootfs: Provide rootfs_do_umounts Anton Mikanovich
2024-10-11 10:00 ` [PATCH v3 6/8] initramfs: Add missing umounts after generation Anton Mikanovich
2024-10-11 10:00 ` [PATCH v3 7/8] rootfs: Add missing umounts in rootfs_postprocess() and rootfs_install() Anton Mikanovich
2024-10-11 10:00 ` [PATCH v3 8/8] image: Do not call rootfs_do_umounts twice Anton Mikanovich
2024-10-15 9:23 ` [PATCH v3 0/8] Hanging mount fixes Baurzhan Ismagulov
2024-10-16 16:06 ` Uladzimir Bely
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=20241011100050.322686-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