From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: Uladzimir Bely <ubely@ilbers.de>,
Florian Bezdeka <florian.bezdeka@siemens.com>,
Anton Mikanovich <amikan@ilbers.de>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH] meta: Drop lazy and recursive unmounts
Date: Thu, 10 Oct 2024 11:43:16 +0200 [thread overview]
Message-ID: <ZwehtJp6hJ7B2LfT@abai.m.ilbers.de> (raw)
In-Reply-To: <ecda24dc-7921-4477-b3ba-dc14a39aa148@siemens.com>
On 2024-10-10 06:33, 'Jan Kiszka' via isar-users wrote:
> No, we should not start to consolidate the umounts again. If we do that,
> we could also drop the warning from the catch-all handler
> build_completed and let it umount everything, as we've done in the past.
> If we don't want this anymore, every individual task that does mounting
> must also do the umounting at its end. And that means even the umount in
> do_rootfs_finalize would become obsolete.
I agree, the vision has always been to mount-umount as locally as possible. To
avoid misunderstanding, it isn't about "consolidate the umounts again" -- the
single goal of the cleanup handler is to warn about the problem; unmounting was
done as a by-product only to return a saner state to the user, as executing
sudo rm -rf build afterwards might delete the host /dev, making the system
unusable.
On the whole, the approach in the patches looks good to us; we'll provide a
consolidated patchset today / tomorrow as long as we don't encounter any
surprises underway.
With kind regards,
Baurzhan
--
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/ZwehtJp6hJ7B2LfT%40abai.m.ilbers.de.
prev parent reply other threads:[~2024-10-10 9:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 10:41 Anton Mikanovich
2024-06-26 6:31 ` Uladzimir Bely
2024-08-28 13:05 ` 'Florian Bezdeka' via isar-users
2024-08-29 9:26 ` Anton Mikanovich
2024-08-29 12:26 ` 'Florian Bezdeka' via isar-users
2024-09-06 14:34 ` Anton Mikanovich
2024-10-01 11:59 ` 'Florian Bezdeka' via isar-users
2024-10-01 12:14 ` 'Jan Kiszka' via isar-users
2024-10-01 12:18 ` 'Florian Bezdeka' via isar-users
2024-10-01 12:28 ` 'Jan Kiszka' via isar-users
2024-10-03 14:37 ` Baurzhan Ismagulov
2024-10-04 7:28 ` 'Florian Bezdeka' via isar-users
2024-10-04 8:00 ` Uladzimir Bely
2024-10-04 8:16 ` 'Jan Kiszka' via isar-users
2024-10-10 4:33 ` 'Jan Kiszka' via isar-users
2024-10-10 9:43 ` Baurzhan Ismagulov [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=ZwehtJp6hJ7B2LfT@abai.m.ilbers.de \
--to=ibr@radix50.net \
--cc=amikan@ilbers.de \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=ubely@ilbers.de \
/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