diff options
author | James Bottomley <James.Bottomley@HansenPartnership.com> | 2016-02-25 17:32:51 +0100 |
---|---|---|
committer | James Bottomley <James.Bottomley@HansenPartnership.com> | 2016-03-30 23:12:22 +0200 |
commit | 4af75df6a410ce76d9f60f27b07e5645ecc2c5ed (patch) | |
tree | d6d9b91265b5ded69629015c5ca1013ef91642cf | |
parent | binfmt_misc: add persistent opened binary handler for containers (diff) | |
download | linux-4af75df6a410ce76d9f60f27b07e5645ecc2c5ed.tar.xz linux-4af75df6a410ce76d9f60f27b07e5645ecc2c5ed.zip |
binfmt_misc: add F option description to documentation
Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
-rw-r--r-- | Documentation/binfmt_misc.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/binfmt_misc.txt b/Documentation/binfmt_misc.txt index 6b1de7058371..ec83bbce547a 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 + emulation is installed and uses the opened image to spawn the + emulator, meaning it is always available once installed, + regardless of how the environment changes. There are some restrictions: |