From: Anton Mikanovich <amikan@ilbers.de>
To: "Gökhan Çetin" <ctngkhn@gmail.com>,
isar-users <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>,
"Baurzhan Ismagulov" <ibr@ilbers.de>
Subject: Re: schroot umount target is busy
Date: Fri, 12 Jul 2024 10:04:34 +0300 [thread overview]
Message-ID: <8a611b46-370e-46f4-8ebc-725f6dbfbef5@ilbers.de> (raw)
In-Reply-To: <f4495e54-a4f3-417d-8b4d-bd38b723a232n@googlegroups.com>
Hello Gökhan,
I've found an issue with isar-apt usage without lock protection in
deb_dl_dir_export and imager_run implementations. This can influence on
umount
issues you've observed, so please try the fix from patchset:
[PATCH 0/2] Protect isar-apt usages in shell
--
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/8a611b46-370e-46f4-8ebc-725f6dbfbef5%40ilbers.de.
next prev parent reply other threads:[~2024-07-12 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 8:47 Schultschik, Sven
2024-06-05 8:55 ` Jan Kiszka
2024-07-08 14:17 ` Gökhan Çetin
2024-07-08 15:13 ` 'Jan Kiszka' via isar-users
2024-07-09 6:28 ` Gökhan Çetin
2024-07-09 6:48 ` Anton Mikanovich
2024-07-12 7:04 ` Anton Mikanovich [this message]
2024-08-06 8:02 ` Anton Mikanovich
2024-08-06 8:19 ` Gökhan Çetin
2024-07-09 6:52 ` 'cedric.hombourger@siemens.com' via isar-users
2024-07-09 10:27 ` 'Jan Kiszka' via isar-users
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=8a611b46-370e-46f4-8ebc-725f6dbfbef5@ilbers.de \
--to=amikan@ilbers.de \
--cc=cedric.hombourger@siemens.com \
--cc=ctngkhn@gmail.com \
--cc=ibr@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