diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2021-04-28 22:22:55 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2021-04-28 22:22:55 -0700 |
| commit | 4541bfa59b37cd226187667951eebed0c5359c83 (patch) | |
| tree | 0e6f5cd801aa32ffe64ac126174ea34b4c9376d7 /104test.subx | |
| parent | dcb6a21a911d61c51d1f54c357b5c6fcb01dd7cc (diff) | |
| download | mu-4541bfa59b37cd226187667951eebed0c5359c83.tar.gz | |
extremely threadbare null-pointer protection
This protects us from reading null arrays, but not null structs. It also doesn't protect us from writes to address 0 itself. It is also incredibly unsafe. According to https://wiki.osdev.org/Memory_Map_(x86), address 0 contains the real-mode IVT. Am I sure it'll never ever get used after I switch to protected mode? I really need a page table, something minimal to protect the first 4KB of physical memory or something. I wonder what other languages/OSs do to protect against really large struct definitions.
Diffstat (limited to '104test.subx')
0 files changed, 0 insertions, 0 deletions