A Deep Dive into the ELF File Format
Elf Quest
Linux and other Unix-based systems use the ELF file format for executables, object code, and shared libraries. Take a peek inside to learn how an ELF file is organized.
An object file is a black box that you can never really see inside. You can't just open it and read it. We all have some understanding that it contains instructions for the computer, coded in a format that only a computer can understand, but we're used to thinking of compiled program code as something of a mystery. If you take a closer look, however, the structure is not as opaque as you might imagine.
Linux, like most other Unix-like operating systems, stores program code in the Executable and Linkable Format (ELF). ELF superseded the less-flexible a.out
format and has been the standard in Linux since 1995 and in FreeBSD [1] since 1998. An ELF object file contains the processor-specific instructions that the CPU actually executes. It also contains other information relating to
- how and where to load the object into memory
- dynamic linking
- any public functions exported (or imported) by the object
- debugging
Much of this functionality is only documented in the source code for kernels and toolchains themselves or in various obscure parts of the web. Understanding the ELF format is essential for anyone writing a compiler, assembler, or linker for the Linux platform.
The best way to study the structure of an ELF file is to watch one come together. In this article, I'll show how to construct an extensible ELF file from scratch using flat assembler (fasm) [2], an x86 macro-assembler. Fasm supports the creation of "flat" binary files, meaning that the programmer determines (broadly speaking) every byte that appears in the output file. The ELF file will run on both Linux and FreeBSD; the full code is about 500 lines, and you can download it from the associated Git repository [3]. You'll need to install fasm from your operating system's package repository.
In your daily life, it is rarely necessary to build an ELF file manually. This exercise is intended for purposes of illustration. In the real world, a developer tool such as a compiler generates the ELF file based on the contents of source code and information provided by the developer.
The Layout of an ELF File
An ELF file usually has four main parts:
- the ELF header
- one or more program headers
- one or more section headers
- one or more sections
Assembly languages operate at a lower level than a language such as C, so assembly language corresponds more closely with the commands the computer actually executes. I'll therefore use assembly language as a means for describing the ELF format. Figure 1 provides a graphical representation of an ELF file and shows how this file relates to the ELF image when loaded into memory.
The ELF Header
In Listing 1, I declare the ELF header (for those new to assembly language, db
means "declare byte," dw
means "declare word" (two bytes), and so on; rept n {}
repeats the enclosed code n
times).
Listing 1
The ELF Header
01 ; Magic. 02 db 0x7f,"ELF" 03 ; Class (32- or 64-bit). 04 db ELFCLASS64 05 ; Endian-ness (least significant bytes 06 ; first). 07 db ELFDATA2LSB 08 ; Version of the ELF spec. 09 db EV_CURRENT 10 ; ABI (Application Binary Interface) - 11 ; we use ELFOSABI_LINUX = 3 or 12 ; ELFOSABI_FREEBSD = 9 13 if OS eq "Linux" 14 db ELFOSABI_LINUX 15 else if OS eq "FreeBSD" 16 db ELFOSABI_FREEBSD 17 end if 18 ; ABI version (always 0). 19 db 0 20 rept 7 {db 0} ; Padding. 21 ; Executable type (2) could also be 22 ; ET_REL = 1 for a relocatable object or 23 ; ET_DYN = 3 for a shared library. 24 dw ET_EXEC 25 ; Machine is x86-64. 26 dw EM_AMD64 27 ; File version (always set to EV_CURRENT 28 ; = 1). 29 dd EV_CURRENT 30 ; Entry point. 31 dq LOAD_BASE + PLANE1 + main 32 ; Program headers offset. 33 dq PROGRAM_HEADERS 34 ; Section headers offset. 35 dq SECTION_HEADERS 36 ; Flags (always 0). 37 dd 0 38 ; Size of this ELF header. 39 dw ELF_HEADER_SIZE 40 ; Size of one program header (56 bytes). 41 dw SIZEOF_PROGRAM_HEADER 42 dw NUM_PROGRAM_HEADERS 43 ; Size of one section header (64 bytes). 44 dw SIZEOF_SECTION_HEADER 45 dw NUM_SECTION_HEADERS 46 ; This is the section header table index 47 ; of the entry associated with the 48 ; section name string table. 49 dw SHSTRTAB_INDEX 50 ELF_HEADER_SIZE = $
As you can see in Listing 1, the ELF header contains general information describing the program's context. For instance, the header contains settings for the class (32-bit or 64-bit), the Endianness, the operating system, the file type (executable, relocatable object, or shared library), and the processor. The ELF header also marks out the space for the program and section headers, which you'll learn about later in this article.
Program Headers
Each program header describes a memory segment in the final loaded image. Program headers don't have any raw data associated with them; they just tell the loader to allocate memory that will be populated with data from one or more sections. Segments can overlap; you can use the overlap to mark the .dynamic
section as both PT_DYNAMIC
and PT_LOAD
. Because I'm declaring multiple segments, I wrap the declarations in a macro (Listing 2).
Listing 2
The Program Header Macro
01 macro PROGRAM_HEADER type,permissions, offset,virtual_address,physical_address, disk_size,mem_size,alignment 02 { 03 ; Segment type - common types are 04 ; PT_NULL = 0; PT_LOAD = 1; 05 ; PT_DYNAMIC = 2; PT_INTERP = 3; 06 ; PT_PHDR = 6. 07 dd type 08 ; Permissions - readable/writable/ 09 ; executable: an ORed combination 10 ; of values from PF_R = 0x4; PF_W = 11 ; 0x2; PF_X = 0x1. 12 dd permissions 13 ; Offset in file. 14 dq offset 15 ; Offset at runtime. 16 dq virtual_address 17 ; Unused; set to 0. 18 dq physical_address 19 dq disk_size 20 dq mem_size 21 dq alignment 22 ; The following variable lets us count ; program headers as we declare them. 23 CPROGRAM_HEADER = CPROGRAM_HEADER + 1 24 }
I can then declare a program header with a single macro invocation:
PROGRAM_HEADER PT_LOAD,PF_R or PF_X,SECTION_TEXT,LOAD_BASE + PLANE1 +SECTION_TEXT,0,TEXT_PLUS_PLT_SIZE,TEXT_PLUS_PLT_SIZE,0x1000
A segment's offset and alignment must obey the following constraint:
offset mod alignment == virtual_address mod alignment && offset mod page_size == virtual_address mod page_size
(where mod
is the integer modulo operator and page_size
is usually 4096 for Linux and FreeBSD). The PLANE*
constants in the source are there to maintain an appropriate minimum distance of page_size
between segments.
Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.
News
-
Linux Sees Massive Performance Increase from a Single Line of Code
With one line of code, Intel was able to increase the performance of the Linux kernel by 4,000 percent.
-
Fedora KDE Approved as an Official Spin
If you prefer the Plasma desktop environment and the Fedora distribution, you're in luck because there's now an official spin that is listed on the same level as the Fedora Workstation edition.
-
New Steam Client Ups the Ante for Linux
The latest release from Steam has some pretty cool tricks up its sleeve.
-
Gnome OS Transitioning Toward a General-Purpose Distro
If you're looking for the perfectly vanilla take on the Gnome desktop, Gnome OS might be for you.
-
Fedora 41 Released with New Features
If you're a Fedora fan or just looking for a Linux distribution to help you migrate from Windows, Fedora 41 might be just the ticket.
-
AlmaLinux OS Kitten 10 Gives Power Users a Sneak Preview
If you're looking to kick the tires of AlmaLinux's upstream version, the developers have a purrfect solution.
-
Gnome 47.1 Released with a Few Fixes
The latest release of the Gnome desktop is all about fixing a few nagging issues and not about bringing new features into the mix.
-
System76 Unveils an Ampere-Powered Thelio Desktop
If you're looking for a new desktop system for developing autonomous driving and software-defined vehicle solutions. System76 has you covered.
-
VirtualBox 7.1.4 Includes Initial Support for Linux kernel 6.12
The latest version of VirtualBox has arrived and it not only adds initial support for kernel 6.12 but another feature that will make using the virtual machine tool much easier.
-
New Slimbook EVO with Raw AMD Ryzen Power
If you're looking for serious power in a 14" ultrabook that is powered by Linux, Slimbook has just the thing for you.