Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1755532AbcKKKbb (ORCPT <rfc822;w@1wt.eu>);
        Fri, 11 Nov 2016 05:31:31 -0500
Received: from mail-wm0-f52.google.com ([74.125.82.52]:38767 "EHLO
        mail-wm0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1754492AbcKKKb3 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 11 Nov 2016 05:31:29 -0500
References: <1471838494-29672-1-git-send-email-JMax@mail.greenriver.edu> <1472141735.3489.5.camel@HansenPartnership.com> <9856acd1-cab7-2691-1c89-279fbfe53e19@redhat.com> <9906de02-1def-22f3-da7a-1040c65d09fd@redhat.com>
User-agent: mu4e 0.9.17; emacs 25.1.50.16
From: Alex =?utf-8?Q?Benn=C3=A9e?= <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
In-reply-to: <9906de02-1def-22f3-da7a-1040c65d09fd@redhat.com>
Date: Fri, 11 Nov 2016 10:31:26 +0000
Message-ID: <87wpga71fl.fsf@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1018
Lines: 28


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