rust-kernel
Rustbelt: a hobby x86_64 kernel written in Rust
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 | //! A tiny ELF64 loader: just enough to load a statically linked user program
//! (execve and spawn use it) -- classic or position independent.
//!
//! An ELF file starts with a header saying what it is (64-bit, little endian,
//! x86_64, executable) and where the *program headers* are. Each program
//! header of type PT_LOAD says: "map `memsz` bytes at virtual address
//! `vaddr`, fill the first `filesz` of them from file offset `offset`, zero
//! the rest (that's .bss), with permissions R/W/X". That's all a loader for a
//! static executable has to do; then jump to `entry`.
//!
//! Stage 19: **static PIE** ("position-independent executable"). Modern
//! toolchains make PIE files by default (e_type ET_DYN): their addresses
//! start at 0 and the program can run anywhere, because it fixes up its own
//! pointers at start-up (musl's `rcrt1.o` does that). We pick a *load
//! bias* -- a random page-aligned base, so every run lands somewhere else
//! (address space layout randomization) -- add it to every address in the
//! file, and tell the program in its auxiliary vector (AT_PHDR, AT_ENTRY).
//! A PIE file that names a *dynamic loader* (PT_INTERP, e.g.
//! /lib/ld-musl-x86_64.so.1) needs shared libraries we don't have: ENOEXEC.
//! Other program headers we look at: PT_GNU_STACK (may the stack be
//! executable?), PT_TLS and PT_GNU_RELRO (just accepted: the C library
//! sets up thread-local storage and makes RELRO read-only by itself).
//!
//! Every number we read comes from an untrusted file, so all offsets and sizes
//! are bounds-checked. Reference: `man 5 elf`, https://wiki.osdev.org/ELF
use crate;
use crate;
use Vec;
use ;
use VirtAddr;
const PT_LOAD: u32 = 1;
const PT_INTERP: u32 = 3;
const PT_TLS: u32 = 7;
const PT_GNU_STACK: u32 = 0x6474_e551;
const PT_GNU_RELRO: u32 = 0x6474_e552;
const ET_EXEC: u16 = 2;
const ET_DYN: u16 = 3;
const PF_X: u32 = 1;
const PF_W: u32 = 2;
/// One PT_LOAD program header.
/// What the ELF header and the program headers say.
/// Check the ELF header and read the program headers.
/// What `load` tells execve about the program (for the auxiliary vector).
/// Where a PIE goes: 512 GiB + 4 MiB (the start of level-4 slot 1, where it
/// always went) plus a random number of pages (up to 1 GiB), so the heap
/// after it and mmap from the top still have hundreds of GiB between them,
/// and plain `gcc -static` programs at 0x400000 are far below it.
const PIE_BASE: u64 = 0x80_0040_0000;
const PIE_RANDOM_PAGES: u64 = 0x4_0000;
/// A random load bias for a PIE whose lowest segment starts at `low`.
/// Parse and check everything (headers, segment bounds, permissions) without
/// mapping anything: execve calls this *before* it destroys the old program,
/// so a bad file can still be reported as an error.
///
/// `random`: pick a random bias for a PIE (else the lowest one, enough to
/// check the file).
/// Load the ELF image `data` into the (empty) address space `mm`: map and
/// fill every segment (eagerly -- programs are small), and record each as
/// a region.
/// Just validate the file (execve before the point of no return, tests).
/// Returns the entry point.
|