From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

binfmt_misc (Miscellaneous Binary Format) is a capability of the Linux kernel which allows arbitrary executable file formats to be recognized and passed to certain user space applications, such as emulators and virtual machines.[1] It is one of a number of binary format handlers in the kernel that are involved in preparing a user-space program to run.[2]

The executable formats are registered through the special purpose file system binfmt_misc file-system interface (usually mounted under part of /proc). This is either done directly by sending special sequences to the register procfs file or using a wrapper like Debian-based distributions binfmt-support package[3] or systemd's systemd-binfmt.service.[4][5]


The register file contains lines which define executable types to be handled. Each line is of the form:


  • name is the name of the binary format.
  • type is either E or M
    • If it is E, the executable file format is identified by its filename extension: magic is the file extension to be associated with the binary format; offset and mask are ignored.
    • If it is M, the format is identified by magic number at an absolute offset (defaults to 0) in the file and mask is a bitmask (defaults to all 0xFF) indicating which bits in the number are significant.
  • interpreter is a program that is to be run with the matching file as an argument.
  • flags (optional) is a string of letters, each controlling a certain aspect of interpreter invocation:
    • P to preserve the original program name typed by user in command line — by adding that name to argv; the interpreter has to be aware of this so it can correctly pass that additional parameter to the interpreted program as its argv[0].
    • O to open the program file and pass its file descriptor to the interpreter so it could read an otherwise unreadable file (for which the user does not have the "Read" permission).
    • C to determine new process credentials based on program file rather than interpreter file (see setuid); implies O flag.
    • F to make the kernel open the binary at configuration time instead of lazily at startup time, so that it is available inside other mount namespaces and chroots as well.

Each format has a corresponding file entry in the /proc/sys/fs/binfmt_misc directory which can be read to get information about a given file format.


$ echo -1 >/proc/sys/fs/binfmt_misc/status # all entries
$ echo -1 >/proc/sys/fs/binfmt_misc/qemu-xtensa # single entry

Common usage[edit]

binfmt_misc allows Java programs to be passed directly to the Java virtual machine.[6]

Another common usage is to execute PE executables (compiled for MS-DOS or Microsoft Windows) through Wine. For example, the following line will run DOS and Windows EXE files (identified by the "MZ" type code) using Wine:


To run EXE (.NET) files with Mono:[7][8] :CLR:M::MZ::/usr/bin/mono:

binfmt_misc can also be combined with QEMU or Box86 to execute programs for other processor architectures as if they were native binaries.[9]

binfmt_misc can be used for Go as a scripting language.[10]

See also[edit]


  1. ^ Kernel Support for miscellaneous Binary Formats (binfmt_misc) The Linux Kernel documentation
  2. ^ How programs get run, January 28, 2015, by David Drysdale,
  3. ^ Details of package binfmt-support in sid, Debian
  4. ^ systemd-binfmt.service,
  5. ^ binfmt.d,
  6. ^ Java(tm) Binary Kernel Support for Linux v1.03 The Linux Kernel documentation
  7. ^ Mono(tm) Binary Kernel Support for Linux The Linux Kernel documentation
  8. ^ Guide:Running Mono Applications
  9. ^ Official QEMU mirror, QEMU
  10. ^ Using Go as a scripting language in Linux, Cloudflare, 2018-02-20, retrieved 2019-05-05

External links[edit]