about summary refs log tree commit diff stats
path: root/translate_subx_emulated
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2021-04-28 22:22:55 -0700
committerKartik K. Agaram <vc@akkartik.com>2021-04-28 22:22:55 -0700
commit4541bfa59b37cd226187667951eebed0c5359c83 (patch)
tree0e6f5cd801aa32ffe64ac126174ea34b4c9376d7 /translate_subx_emulated
parentdcb6a21a911d61c51d1f54c357b5c6fcb01dd7cc (diff)
downloadmu-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 'translate_subx_emulated')
0 files changed, 0 insertions, 0 deletions
2595c41fda72f67284b101f509524e659'>^
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