linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	containers@lists.linux-foundation.org,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [Patch v2 3/3] binfmt_misc: add F option description to documentation
Date: Sun, 28 Feb 2016 21:32:26 -0800	[thread overview]
Message-ID: <56D3D7EA.2090602@infradead.org> (raw)
In-Reply-To: <1456429136.2377.7.camel@HansenPartnership.com>

On 02/25/16 11:38, James Bottomley wrote:
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> ---
>  Documentation/binfmt_misc.txt | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/Documentation/binfmt_misc.txt b/Documentation/binfmt_misc.txt
> index 6b1de70..a22eb69 100644
> --- a/Documentation/binfmt_misc.txt
> +++ b/Documentation/binfmt_misc.txt
> @@ -66,6 +66,13 @@ Here is what the fields mean:
>              This feature should be used with care as the interpreter
>              will run with root permissions when a setuid binary owned by root
>              is run with binfmt_misc.
> +      'F' - fix binary.  The usual behaviour of binfmt_misc is to spawn the
> +      	    binary lazily when the misc format file is invoked.  However,
> +	    this doesn't work very well in the face of mount namespaces and
> +	    changeroots, so the F mode opens the binary as soon as the
> +	    emultation is installed and uses the opened image to spawn the

	    emulation

> +	    emulator, meaning it is always available once installed,
> +	    regardless of how the environment changes.
>  
>  
>  There are some restrictions:
> 


-- 
~Randy

      reply	other threads:[~2016-02-29  5:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 19:34 [Patch v2 0/3] allow the creation of architecture emulation containers where the emulator binary is outside the container James Bottomley
2016-02-25 19:36 ` [Patch v2 1/3] fs: add filp_clone_open API James Bottomley
2016-03-08  6:19   ` Serge E. Hallyn
2016-03-08  9:17   ` Mateusz Guzik
2016-03-08 11:19     ` James Bottomley
2016-02-25 19:37 ` [Patch v2 2/3] binfmt_misc: add persistent opened binary handler for containers James Bottomley
2016-03-08  8:10   ` Serge E. Hallyn
2016-02-25 19:38 ` [Patch v2 3/3] binfmt_misc: add F option description to documentation James Bottomley
2016-02-29  5:32   ` Randy Dunlap [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=56D3D7EA.2090602@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-fsdevel@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).