about summary refs log tree commit diff stats
path: root/106stream.subx
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 /106stream.subx
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 '106stream.subx')
0 files changed, 0 insertions, 0 deletions
functionaltests.c?id=5e324e407fda7d616c8b6056495de9db1d5a49e0'>5e324e40 ^
c6ff761a ^
d54cbf12 ^
f9a7e350 ^
de747e3d ^
87b4d7cb ^
e1e0fda8 ^
97c5072f ^
52e2917b ^

97c5072f ^


e295a474 ^
377a63d0 ^





f189dbc6 ^




377a63d0 ^














2b7894cc ^
377a63d0 ^

373f47c7 ^
52e2917b ^
6303e0e2 ^


377a63d0 ^











fca59a31 ^
377a63d0 ^


a978bb12 ^
377a63d0 ^












377a63d0 ^







ee664bf1 ^

69ac8097 ^


e1e0fda8 ^

97c5072f ^



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