From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: Florian Weimer <fweimer@redhat.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Josh Max <JMax@mail.greenriver.edu>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] binfmt_misc: allow selecting the interpreter based on xattr keywords
Date: Fri, 11 Nov 2016 10:31:26 +0000 [thread overview]
Message-ID: <87wpga71fl.fsf@linaro.org> (raw)
In-Reply-To: <9906de02-1def-22f3-da7a-1040c65d09fd@redhat.com>
Carlos O'Donell <carlos@redhat.com> writes:
> On 08/26/2016 10:55 AM, Florian Weimer wrote:
>> On 08/25/2016 06:15 PM, James Bottomley wrote:
>>> On Sun, 2016-08-21 at 21:01 -0700, Josh Max wrote:
<snip>
>
> This ignores the fact that the alternate loader also needs to have
> it's own ldconfig cache, implementation-dependent lookup paths etc,
> all of which have to be keyed off the xattr keyword specified dynamic
> loader. All of that is tractable though and can be done in userspace
> keyed from the selected dynamic loader. Buy why? Why not use a mount
> namespace and different loader e.g. lxc, docker, etc, or specify a
> loader that is a wrapper and does this for you?
Is binfmt_misc actually containerise-able yet? At the moment when using
qemu-user inside a docker container I still have to ensure the root
binfmt_misc points to the same location as I place qemu-user in the
docker container.
>
> I'm not convinced this is a good idea, but I'm open to learning about
> more use cases.
--
Alex Bennée
next prev parent reply other threads:[~2016-11-11 10:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 4:01 [PATCH] binfmt_misc: allow selecting the interpreter based on xattr keywords Josh Max
2016-08-25 16:15 ` James Bottomley
2016-08-26 8:00 ` Josh Max
2016-08-26 14:55 ` Florian Weimer
2016-08-26 17:59 ` Carlos O'Donell
2016-08-26 21:38 ` James Bottomley
2016-11-11 10:31 ` Alex Bennée [this message]
2016-08-26 21:12 ` One Thousand Gnomes
2016-08-26 21:26 ` James Bottomley
2016-08-27 11:52 ` One Thousand Gnomes
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=87wpga71fl.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=JMax@mail.greenriver.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).