From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta: do not share dev mounts
Date: Fri, 17 Jun 2022 20:07:21 +0300 [thread overview]
Message-ID: <e63b3082-9e99-73dc-5023-4203de662e7e@ilbers.de> (raw)
In-Reply-To: <20220610084437.7490-1-amikan@ilbers.de>
10.06.2022 11:44, Anton Mikanovich wrote:
> As /dev was mounted into bootstrap/rootfs/buildchroot in shared mode
> it made the first ended task unmount /dev/shm or /dev/pts for all other
> tasks executed at the moment.
> To prevent mounts corruption make /dev to be mounted as private.
> This will protect mountpoints from all the propagations during the task
> execution.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
Applied to next.
prev parent reply other threads:[~2022-06-17 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 8:44 Anton Mikanovich
2022-06-17 17:07 ` Anton Mikanovich [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=e63b3082-9e99-73dc-5023-4203de662e7e@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