Kernel: Allocate shared memory regions immediately

Lazily committed shared memory was not working in situations where one
process would write to the memory and another would only read from it.

Since the reading process would never cause a write fault in the shared
region, we'd never notice that the writing process had added real
physical pages to the VMObject. This happened because the lazily
committed pages were marked "present" in the page table.

This patch solves the issue by always allocating shared memory up front
and not trying to be clever about it.

1 files changed, 6 insertions, 0 deletions

diff --git a/Kernel/VM/Region.cpp b/Kernel/VM/Region.cpp
index 62ef18995e..52b29aad26 100644
--- a/Kernel/VM/Region.cpp
+++ b/Kernel/VM/Region.cpp
@@ -282,6 +282,12 @@ bool Region::map_individual_page_impl(size_t page_index)
     if (!page || (!is_readable() && !is_writable())) {
         pte->clear();
     } else {
+        if (is_shared()) {
+            // Shared memory should not be lazily populated!
+            ASSERT(!page->is_shared_zero_page());
+            ASSERT(!page->is_lazy_committed_page());
+        }
+
         pte->set_cache_disabled(!m_cacheable);
         pte->set_physical_page_base(page->paddr().get());
         pte->set_present(true);