<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Memfd on Nalar</title>
    <link>https://nalar.dev/tags/memfd/</link>
    <description>Recent content in Memfd on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/memfd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Memfd Seals Turn Shared Memory Into Monotonic File Policy</title>
      <link>https://nalar.dev/memfd-seals-turn-shared-memory-into-monotonic-file-policy/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/memfd-seals-turn-shared-memory-into-monotonic-file-policy/</guid>
      <description>&lt;h1 id=&#34;memfd-seals-turn-shared-memory-into-monotonic-file-policy&#34;&gt;Memfd Seals Turn Shared Memory Into Monotonic File Policy&lt;/h1&gt;&#xA;&lt;p&gt;A process prepares a binary object in memory, passes its file descriptor to another process, and expects the bytes to remain stable after validation. Ordinary shared memory does not provide that property by itself: another holder of writable authority can change the object after a check, resize it, or keep a writable mapping alive. Linux file seals provide a narrower contract. They remove selected mutation operations from a sealable file, and successfully added seals cannot later be removed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
