Skip to content

docs(p15-initproc): add missing question mark #361

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
himanshi1505 wants to merge 1 commit into
base: p15-initproc
Choose a base branch
from
Open

docs(p15-initproc): add missing question mark #361

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion p15-initproc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ its code segment selector base set as `STARTPROC`.

Virtualizing memory only partly solves the isolation problem. What stops a
process from calling instructions like `lgdt` and `lidt` to take control of the
memory segments and the interrupts. If a process wants to illegally overwrite OS
memory segments and the interrupts? If a process wants to illegally overwrite OS
code, it can setup its own GDT by calling `lgdt` like in `seginit` in `vm.c` to
give itself permission to access other parts of memory.

Expand Down