Skip to content

Correct ring usage description in memory section #63

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
srinathln7 wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

Correct ring usage description in memory section #63

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 src/chp4/sw_stack_1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,7 @@ It's important you commit it to memory, pun intended.
> The kernel runs in "ring 0", the most privileged mode available.
> It can read/write from/to any processes's memory, directly access hardware, and control special CPU features.
>
> Rings 2 and 3 are almost never used in practice[^RingProt].
> Rings 1 and 2 are almost never used in practice[^RingProt].
> These modes were intended for device drivers, special programs that allow a kernel to communicate with vendor-specific hardware.
> In reality most device drivers are loaded directly into the kernel, running alongside it in ring 0 (creating a major OS attack surface[^MSKernBlocklist]).
>
Expand Down