<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Page Faults on Nalar</title>
    <link>https://nalar.dev/tags/page-faults/</link>
    <description>Recent content in Page Faults on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/page-faults/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>userfaultfd Write Protection Turns Memory Writes into Userspace Events</title>
      <link>https://nalar.dev/userfaultfd-write-protection-turns-memory-writes-into-userspace-events/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/userfaultfd-write-protection-turns-memory-writes-into-userspace-events/</guid>
      <description>&lt;p&gt;A thread can reach a valid, resident page and still stop before modifying it. With Linux &lt;code&gt;userfaultfd&lt;/code&gt; write-protect mode, a registered page can be marked so that a write generates a userfaultfd page-fault event. A userspace handler receives that event, performs its bookkeeping, removes the protection, and lets the blocked thread continue.&lt;/p&gt;&#xA;&lt;p&gt;The mechanism sits between ordinary page permissions and application-level memory accounting. The page remains part of the process address space; the kernel redirects the write fault into a file-descriptor protocol instead of forcing the application to build the same control path around &lt;code&gt;mprotect()&lt;/code&gt; and &lt;code&gt;SIGSEGV&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
