How exactly does the OS protect the kernel?

My question is exactly how the operating system protects its part of the kernel.

From what I found, there are basically 2 kernel and user modes. And there must be several bits in the memory segments if the memory segment is a kernel or user space segment. But where is the origin of these bits? Is there any kind of “switch” in the compiler that marks programs as kernel programs? And, for example, if the driver is in kernel mode, how does the OS manage its integration into the system, so malware is not added as a driver?

If someone could enlighten me on this issue, I would be very grateful, thanks

+5
source share
4 answers

- memmory, .

, , . , , MMU RAM, "" . , .

, , , MMU .

, , , MMU , , , MMU , .

"" , , , ​​ .

, , , SEGFAULT, .

, , , MMU .

(, 80286) (, ARM CortexM3 Attiny), MMU, , 1 1 RAM

+5

"" . (a.k.a. ring 0 i386). . . :

  • .

.

+5

, . . ​​ .

0
  

, , , , ?

  

. :

  • Linux: . :

a) , EXPORT_SYMBOL. . ​​ . , EXPORT_SYMBOL, .

b) , root. , root , .

  • -, QNX: , . , , , .
0
source

All Articles