2019-05-19 12:07:45 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2018-07-31 11:39:34 +00:00
|
|
|
|
|
|
|
menu "Executable file formats"
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config BINFMT_ELF
|
|
|
|
bool "Kernel support for ELF binaries"
|
2018-03-07 22:30:54 +00:00
|
|
|
depends on MMU
|
2016-05-23 23:22:26 +00:00
|
|
|
select ELFCORE
|
2005-04-16 22:20:36 +00:00
|
|
|
default y
|
|
|
|
---help---
|
|
|
|
ELF (Executable and Linkable Format) is a format for libraries and
|
|
|
|
executables used across different architectures and operating
|
|
|
|
systems. Saying Y here will enable your kernel to run ELF binaries
|
|
|
|
and enlarge it by about 13 KB. ELF support under Linux has now all
|
|
|
|
but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
|
|
|
|
because it is portable (this does *not* mean that you will be able
|
|
|
|
to run executables from different architectures or operating systems
|
|
|
|
however) and makes building run-time libraries very easy. Many new
|
|
|
|
executables are distributed solely in ELF format. You definitely
|
|
|
|
want to say Y here.
|
|
|
|
|
|
|
|
Information about ELF is contained in the ELF HOWTO available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
|
|
|
|
If you find that after upgrading from Linux kernel 1.2 and saying Y
|
|
|
|
here, you still can't run any ELF binaries (they just crash), then
|
|
|
|
you'll have to install the newest ELF runtime libraries, including
|
|
|
|
ld.so (check the file <file:Documentation/Changes> for location and
|
|
|
|
latest version).
|
|
|
|
|
2008-01-30 12:31:46 +00:00
|
|
|
config COMPAT_BINFMT_ELF
|
|
|
|
bool
|
2008-10-16 05:04:17 +00:00
|
|
|
depends on COMPAT && BINFMT_ELF
|
2016-05-23 23:22:26 +00:00
|
|
|
select ELFCORE
|
2008-01-30 12:31:46 +00:00
|
|
|
|
binfmt_elf: allow arch code to examine PT_LOPROC ... PT_HIPROC headers
MIPS is introducing new variants of its O32 ABI which differ in their
handling of floating point, in order to enable a gradual transition
towards a world where mips32 binaries can take advantage of new hardware
features only available when configured for certain FP modes. In order
to do this ELF binaries are being augmented with a new section that
indicates, amongst other things, the FP mode requirements of the binary.
The presence & location of such a section is indicated by a program
header in the PT_LOPROC ... PT_HIPROC range.
In order to allow the MIPS architecture code to examine the program
header & section in question, pass all program headers in this range
to an architecture-specific arch_elf_pt_proc function. This function
may return an error if the header is deemed invalid or unsuitable for
the system, in which case that error will be returned from
load_elf_binary and upwards through the execve syscall.
A means is required for the architecture code to make a decision once
it is known that all such headers have been seen, but before it is too
late to return from an execve syscall. For this purpose the
arch_check_elf function is added, and called once, after all PT_LOPROC
to PT_HIPROC headers have been passed to arch_elf_pt_proc but before
the code which invoked execve has been lost. This enables the
architecture code to make a decision based upon all the headers present
in an ELF binary and its interpreter, as is required to forbid
conflicting FP ABI requirements between an ELF & its interpreter.
In order to allow data to be stored throughout the calls to the above
functions, struct arch_elf_state is introduced.
Finally a variant of the SET_PERSONALITY macro is introduced which
accepts a pointer to the struct arch_elf_state, allowing it to act
based upon state observed from the architecture specific program
headers.
Signed-off-by: Paul Burton <paul.burton@imgtec.com>
Cc: linux-mips@linux-mips.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Patchwork: https://patchwork.linux-mips.org/patch/7679/
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
2014-09-11 07:30:16 +00:00
|
|
|
config ARCH_BINFMT_ELF_STATE
|
|
|
|
bool
|
|
|
|
|
2020-03-16 16:50:43 +00:00
|
|
|
config ARCH_USE_GNU_PROPERTY
|
|
|
|
bool
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config BINFMT_ELF_FDPIC
|
|
|
|
bool "Kernel support for FDPIC ELF binaries"
|
2017-08-11 04:53:39 +00:00
|
|
|
default y if !BINFMT_ELF
|
2018-03-07 22:30:54 +00:00
|
|
|
depends on (ARM || (SUPERH32 && !MMU) || C6X)
|
2016-05-23 23:22:26 +00:00
|
|
|
select ELFCORE
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
ELF FDPIC binaries are based on ELF, but allow the individual load
|
|
|
|
segments of a binary to be located in memory independently of each
|
|
|
|
other. This makes this format ideal for use in environments where no
|
|
|
|
MMU is available as it still permits text segments to be shared,
|
|
|
|
even if data segments are not.
|
|
|
|
|
|
|
|
It is also possible to run FDPIC ELF binaries on MMU linux also.
|
|
|
|
|
2016-05-23 23:22:26 +00:00
|
|
|
config ELFCORE
|
|
|
|
bool
|
|
|
|
help
|
|
|
|
This option enables kernel/elfcore.o.
|
|
|
|
|
2008-10-19 03:28:23 +00:00
|
|
|
config CORE_DUMP_DEFAULT_ELF_HEADERS
|
|
|
|
bool "Write ELF core dumps with partial segments"
|
2010-10-27 22:34:09 +00:00
|
|
|
default y
|
2009-01-10 00:40:52 +00:00
|
|
|
depends on BINFMT_ELF && ELF_CORE
|
2008-10-19 03:28:23 +00:00
|
|
|
help
|
|
|
|
ELF core dump files describe each memory mapping of the crashed
|
|
|
|
process, and can contain or omit the memory contents of each one.
|
|
|
|
The contents of an unmodified text mapping are omitted by default.
|
|
|
|
|
|
|
|
For an unmodified text mapping of an ELF object, including just
|
|
|
|
the first page of the file in a core dump makes it possible to
|
|
|
|
identify the build ID bits in the file, without paying the i/o
|
|
|
|
cost and disk space to dump all the text. However, versions of
|
|
|
|
GDB before 6.7 are confused by ELF core dump files in this format.
|
|
|
|
|
|
|
|
The core dump behavior can be controlled per process using
|
|
|
|
the /proc/PID/coredump_filter pseudo-file; this setting is
|
|
|
|
inherited. See Documentation/filesystems/proc.txt for details.
|
|
|
|
|
|
|
|
This config option changes the default setting of coredump_filter
|
2010-10-27 22:34:09 +00:00
|
|
|
seen at boot time. If unsure, say Y.
|
2008-10-19 03:28:23 +00:00
|
|
|
|
2013-04-30 22:27:44 +00:00
|
|
|
config BINFMT_SCRIPT
|
|
|
|
tristate "Kernel support for scripts starting with #!"
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
Say Y here if you want to execute interpreted scripts starting with
|
|
|
|
#! followed by the path to an interpreter.
|
|
|
|
|
|
|
|
You can build this support as a module; however, until that module
|
|
|
|
gets loaded, you cannot run scripts. Thus, if you want to load this
|
|
|
|
module from an initramfs, the portion of the initramfs before loading
|
|
|
|
this module must consist of compiled binaries only.
|
|
|
|
|
|
|
|
Most systems will not boot if you say M or N here. If unsure, say Y.
|
|
|
|
|
2019-06-13 07:08:57 +00:00
|
|
|
config ARCH_HAS_BINFMT_FLAT
|
|
|
|
bool
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config BINFMT_FLAT
|
2008-04-29 07:59:02 +00:00
|
|
|
bool "Kernel support for flat binaries"
|
2019-06-13 07:08:57 +00:00
|
|
|
depends on ARCH_HAS_BINFMT_FLAT
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
Support uClinux FLAT format binaries.
|
|
|
|
|
2019-06-13 07:08:51 +00:00
|
|
|
config BINFMT_FLAT_ARGVP_ENVP_ON_STACK
|
|
|
|
bool
|
|
|
|
|
2019-06-13 07:08:50 +00:00
|
|
|
config BINFMT_FLAT_OLD_ALWAYS_RAM
|
|
|
|
bool
|
|
|
|
|
2019-06-13 07:08:58 +00:00
|
|
|
config BINFMT_FLAT_OLD
|
|
|
|
bool "Enable support for very old legacy flat binaries"
|
|
|
|
depends on BINFMT_FLAT
|
|
|
|
help
|
|
|
|
Support decade old uClinux FLAT format binaries. Unless you know
|
|
|
|
you have some of those say N here.
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config BINFMT_ZFLAT
|
|
|
|
bool "Enable ZFLAT support"
|
|
|
|
depends on BINFMT_FLAT
|
|
|
|
select ZLIB_INFLATE
|
|
|
|
help
|
|
|
|
Support FLAT format compressed binaries
|
|
|
|
|
|
|
|
config BINFMT_SHARED_FLAT
|
|
|
|
bool "Enable shared FLAT support"
|
|
|
|
depends on BINFMT_FLAT
|
|
|
|
help
|
|
|
|
Support FLAT shared libraries
|
|
|
|
|
2008-06-17 11:19:34 +00:00
|
|
|
config HAVE_AOUT
|
|
|
|
def_bool n
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config BINFMT_AOUT
|
|
|
|
tristate "Kernel support for a.out and ECOFF binaries"
|
2008-06-17 11:19:34 +00:00
|
|
|
depends on HAVE_AOUT
|
2005-04-16 22:20:36 +00:00
|
|
|
---help---
|
|
|
|
A.out (Assembler.OUTput) is a set of formats for libraries and
|
|
|
|
executables used in the earliest versions of UNIX. Linux used
|
|
|
|
the a.out formats QMAGIC and ZMAGIC until they were replaced
|
|
|
|
with the ELF format.
|
|
|
|
|
|
|
|
The conversion to ELF started in 1995. This option is primarily
|
|
|
|
provided for historical interest and for the benefit of those
|
|
|
|
who need to run binaries from that era.
|
|
|
|
|
|
|
|
Most people should answer N here. If you think you may have
|
|
|
|
occasional use for this format, enable module support above
|
|
|
|
and answer M here to compile this support as a module called
|
|
|
|
binfmt_aout.
|
|
|
|
|
|
|
|
If any crucial components of your system (such as /sbin/init
|
|
|
|
or /lib/ld.so) are still in a.out format, you will have to
|
|
|
|
say Y here.
|
|
|
|
|
|
|
|
config OSF4_COMPAT
|
|
|
|
bool "OSF/1 v4 readv/writev compatibility"
|
|
|
|
depends on ALPHA && BINFMT_AOUT
|
|
|
|
help
|
|
|
|
Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
|
|
|
|
with v4 shared libraries freely available from Compaq. If you're
|
|
|
|
going to use shared libraries from Tru64 version 5.0 or later, say N.
|
|
|
|
|
|
|
|
config BINFMT_EM86
|
|
|
|
tristate "Kernel support for Linux/Intel ELF binaries"
|
|
|
|
depends on ALPHA
|
|
|
|
---help---
|
|
|
|
Say Y here if you want to be able to execute Linux/Intel ELF
|
|
|
|
binaries just like native Alpha binaries on your Alpha machine. For
|
|
|
|
this to work, you need to have the emulator /usr/bin/em86 in place.
|
|
|
|
|
|
|
|
You can get the same functionality by saying N here and saying Y to
|
|
|
|
"Kernel support for MISC binaries".
|
|
|
|
|
|
|
|
You may answer M to compile the emulation support as a module and
|
|
|
|
later load the module when you want to use a Linux/Intel binary. The
|
|
|
|
module will be called binfmt_em86. If unsure, say Y.
|
|
|
|
|
|
|
|
config BINFMT_MISC
|
|
|
|
tristate "Kernel support for MISC binaries"
|
|
|
|
---help---
|
|
|
|
If you say Y here, it will be possible to plug wrapper-driven binary
|
|
|
|
formats into the kernel. You will like this especially when you use
|
|
|
|
programs that need an interpreter to run like Java, Python, .NET or
|
|
|
|
Emacs-Lisp. It's also useful if you often run DOS executables under
|
|
|
|
the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
|
|
|
|
<http://www.tldp.org/docs.html#howto>). Once you have
|
|
|
|
registered such a binary class with the kernel, you can start one of
|
|
|
|
those programs simply by typing in its name at a shell prompt; Linux
|
|
|
|
will automatically feed it to the correct interpreter.
|
|
|
|
|
|
|
|
You can do other nice things, too. Read the file
|
2018-05-08 18:14:57 +00:00
|
|
|
<file:Documentation/admin-guide/binfmt-misc.rst> to learn how to use this
|
2016-10-18 12:12:27 +00:00
|
|
|
feature, <file:Documentation/admin-guide/java.rst> for information about how
|
|
|
|
to include Java support. and <file:Documentation/admin-guide/mono.rst> for
|
2005-04-16 22:20:36 +00:00
|
|
|
information about how to include Mono-based .NET support.
|
|
|
|
|
|
|
|
To use binfmt_misc, you will need to mount it:
|
|
|
|
mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc
|
|
|
|
|
|
|
|
You may say M here for module support and later load the module when
|
|
|
|
you have use for it; the module is called binfmt_misc. If you
|
|
|
|
don't know what to answer at this point, say Y.
|
2012-10-05 00:15:23 +00:00
|
|
|
|
|
|
|
config COREDUMP
|
|
|
|
bool "Enable core dump support" if EXPERT
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
This option enables support for performing core dumps. You almost
|
|
|
|
certainly want to say Y here. Not necessary on systems that never
|
|
|
|
need debugging or only ever run flawless code.
|
2018-07-31 11:39:34 +00:00
|
|
|
|
|
|
|
endmenu
|