From: DJ Delorie <dj@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [patch v3] Allow for unpriviledged nested containers
Date: Thu, 18 Nov 2021 13:37:22 -0500 [thread overview]
Message-ID: <xny25l1fa5.fsf@greed.delorie.com> (raw)
In-Reply-To: <87wnl5hf2f.fsf@oldenburg.str.redhat.com>
Florian Weimer <fweimer@redhat.com> writes:
> Do we actually need to enter a PID namespace?
Well, for the pldd test, obviously we do ;-)
> Maybe we should do that only if we know we can mount /proc in the
> namespace.
So given three options:
1. No /proc
2. /proc in wrong namespace
3. /proc in correct namespace
We'd prefer 3, then 1, but not 2?
next prev parent reply other threads:[~2021-11-18 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 23:08 DJ Delorie
2021-11-17 11:06 ` Florian Weimer
2021-11-17 22:44 ` DJ Delorie
2021-11-18 11:35 ` Florian Weimer
2021-11-18 18:37 ` DJ Delorie [this message]
2021-11-18 19:47 ` Florian Weimer
2021-11-18 19:52 ` DJ Delorie
2021-11-18 19:55 ` Florian Weimer
2021-11-18 20:18 ` DJ Delorie
2021-11-18 20:20 ` Florian Weimer
2021-11-18 20:25 ` DJ Delorie
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=xny25l1fa5.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).