about summary refs log tree commit diff stats
path: root/shell
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 /shell
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 'shell')
0 files changed, 0 insertions, 0 deletions
ti/profani-tty/commit/tests/functionaltests/test_ping.c?id=b8c94376aad2d5edf4390e47b8dc89db8ab1a517'>b8c94376 ^
7f98e013 ^
f17afcf5 ^

a522d022 ^
f17afcf5 ^


b8c94376 ^
7f98e013 ^
f17afcf5 ^

a522d022 ^
f17afcf5 ^




a48b9fce ^
f17afcf5 ^

7f98e013 ^

f17afcf5 ^



7f98e013 ^
f17afcf5 ^

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