Kernel zeroes memory?

by

On any modern operating system, the only way newly obtained memory will contain nonzero values is if memory previously freed by your program got reused by malloc. When new memory is obtained from the operating system (kernel), it is initially purely virtual. It has no physical existence; instead it is mapped as copy-on-write mappings of a single shared memory page that’s full of 0 bytes. The first time you attempt to write to it, the kernel will trap the write, allocate a new page of physical memory, copy the contents of the original page (which in this case are all 0 bytes) to the new page, and then resume your program. If the kernel knows the newly allocated physical memory is already zero-filled, it might even be able to optimize out the copy step.

This procedure is both necessary and efficient. It’s necessary because handing over memory that might contain private data from the kernel or another user’s processes to your process would be a critical security breach. It’s efficient because no zeroing is performed at allocation time; the “zero-filled” pages are just reference to a shared zero page.

More Related Contents:

  1. /proc/[pid]/pagemaps and /proc/[pid]/maps | linux
  2. How can I get the size of an array from a pointer in C?
  3. Difference between static memory allocation and dynamic memory allocation
  4. Where in memory are my variables stored in C?
  5. When you exit a C application, is the malloc-ed memory automatically freed?
  6. Why is malloc not “using up” the memory on my computer?
  7. Linux Kernel: System call hooking example
  8. Maximum memory which malloc can allocate
  9. Measure time in Linux – time vs clock vs getrusage vs clock_gettime vs gettimeofday vs timespec_get?
  10. What does the brk() system call do?
  11. What are vdso and vsyscall?
  12. Where are constant variables stored in C?
  13. Building a kernel module from several source files which one of them has the same name as the module
  14. How to access mmaped /dev/mem without crashing the Linux kernel?
  15. malloc implementation?
  16. Is there a macro definition to check the Linux kernel version?
  17. Rationale behind the container_of macro in linux/list.h
  18. can size of array be determined at run time in c?
  19. Using realloc to shrink the allocated memory
  20. Why / when to use `intptr_t` for type-casting in C?
  21. Force free() to return malloc memory back to OS
  22. Why my kernel log is not showing the latest output?
  23. Size of stack and heap memory [duplicate]
  24. dynamic memory for 2D char array
  25. What does request_mem_region() actually do and when it is needed?
  26. How to create a new Linux kernel scheduler
  27. addr2line on kernel module
  28. Is it safe to use realloc?
  29. Efficient way to find task_struct by pid
  30. Where can I find system call source code?

Leave a Comment