From: Jan Kiszka <jan.kiszka@siemens.com>
To: <isar-users@googlegroups.com>
Subject: Re: [PATCH] Avoid sharing of /dev/shm from the build context
Date: Fri, 18 Mar 2022 16:46:18 +0100 [thread overview]
Message-ID: <b0108483-44e9-c29a-4c07-a86f4593c419@siemens.com> (raw)
In-Reply-To: <YjSc9/yjxWX6rT30@ilbers.de>
On 18.03.22 15:53, Baurzhan Ismagulov wrote:
> On Fri, Mar 18, 2022 at 02:08:50PM +0100, Jan Kiszka wrote:
>>> I'd personally convert that to if because I never remember the failure behavior
>>
>> You mean && - sure.
>
> Or like this.
>
>
>>> in subshells. While at it, I'd also combine to a single mount -o rbind,rslave
>>> to avoid potential shared mount windows.
>>>
>>> I think that mounting every directory explicitly (bind instead of rbind)
>>> provides more control and avoids a bunch of issues with recursive mounts.
>>
>> Do we know what all needs to be mounted then?
>
> As far as I remember, /dev and /dev/shm were necessary for building; /dev/pts
> was only necessary for interactive work (e.g. sudo).
>
OK, then let's drop the rest and see what explodes. ;)
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2022-03-18 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 17:37 Jan Kiszka
2022-03-17 18:05 ` Jan Kiszka
2022-03-18 9:13 ` Baurzhan Ismagulov
2022-03-18 13:08 ` Jan Kiszka
2022-03-18 14:53 ` Baurzhan Ismagulov
2022-03-18 15:46 ` Jan Kiszka [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=b0108483-44e9-c29a-4c07-a86f4593c419@siemens.com \
--to=jan.kiszka@siemens.com \
--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