From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: Anton Mikanovich <amikan@ilbers.de>, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH v1 5/5] events: Unmount all lost mounts at task fail
Date: Mon, 12 Jul 2021 18:08:55 +0200 [thread overview]
Message-ID: <20210712160855.GA18446@yssyq.m.ilbers.de> (raw)
In-Reply-To: <24de0200-d23e-0fe4-9db1-d876ca6fa55a@siemens.com>
On Thu, Jul 08, 2021 at 06:28:38PM +0200, Jan Kiszka wrote:
> >> No looping, so everything you miss here will continue to be cleaned up
> >> by build_completed() - so what's the point of these changes?
...
> I do get the idea of a perfect world where a single attempt to umount
> works and cleanly pairs with the regular umount when the task succeeds.
> The problem is that I cannot see that this has been validate to truly
> catch the corner cases that the lazy, late-triggered scheme addresses so
> far. If it does not handle that, these umounts are pointless. If it
> does, we can drop the build_completed() handler. Having both indicates
> no progress, just more complexity.
Thanks Jan for the review and the use cases,
I agree that some patches could be refined and better documented.
We'll work on the topics you've raised and respond. I'm afraid we'd need your
help regarding reproducing and analysis of the old issues, because in general,
many issues so far have been rarely reproducible across different build hosts.
With kind regards,
Baurzhan.
prev parent reply other threads:[~2021-07-12 16:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 16:38 [PATCH v1 0/5] Restore downstream mounts compatibility Anton Mikanovich
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 [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=20210712160855.GA18446@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--cc=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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