https://sankethbk.github.io/blog/tags/virtual-memory/Recent content in Virtual Memory on Sanketh's BlogHugo -- 0.163.3en-usFri, 26 Jun 2026 00:00:00 +0000https://sankethbk.github.io/blog/posts/operating-systems/linux/2026-06-26-the-process-address-space/Fri, 26 Jun 2026 00:00:00 +0000https://sankethbk.github.io/blog/posts/operating-systems/linux/2026-06-26-the-process-address-space/<h2 id="the-process-address-space--intro">The Process Address Space — Intro</h2> <p>Same flat (single contiguous range) address space model you already have from the article — nothing new conceptually. Key term to lock in: a <strong>memory area</strong> (this book&rsquo;s name for what the article calls a <strong>VMA</strong>) is a permission-tagged interval within that address space. Access outside any valid area, or against an area&rsquo;s permissions (write to read-only, execute non-executable) → segfault.</p> <p>The list of &ldquo;what memory areas contain&rdquo; is just a slightly different cut of the same segments from the article: text, data, bss, stack, shared library mappings, mmap&rsquo;d files, shared memory, anonymous mappings (<code>malloc</code>). All non-overlapping — every valid address belongs to exactly one area.</p>