<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IPC on Nalar</title>
    <link>https://nalar.dev/tags/ipc/</link>
    <description>Recent content in IPC on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/ipc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Create Sealable In-Memory Files on Linux with memfd_create</title>
      <link>https://nalar.dev/create-sealable-in-memory-files-on-linux-with-memfd-create/</link>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/create-sealable-in-memory-files-on-linux-with-memfd-create/</guid>
      <description>&lt;p&gt;Applications often need a temporary chunk of data that behaves like a file without needing a persistent pathname. A process may build a configuration snapshot, compiled artifact, or serialized message, then map it into memory or pass it to another process.&lt;/p&gt;&#xA;&lt;p&gt;A regular temporary file can do that, but it introduces filesystem naming, cleanup, permissions, and lifetime concerns. An anonymous &lt;code&gt;mmap()&lt;/code&gt; avoids the pathname, but it does not produce an ordinary file descriptor that can be passed to APIs expecting file-backed data.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Pass Open File Descriptors Between Linux Processes with SCM_RIGHTS</title>
      <link>https://nalar.dev/pass-open-file-descriptors-between-linux-processes-with-scm-rights/</link>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/pass-open-file-descriptors-between-linux-processes-with-scm-rights/</guid>
      <description>&lt;p&gt;Processes often need to hand each other access to an already-open resource. A supervisor may accept a client connection and delegate it to a worker. A privileged helper may open a protected file, then give an unprivileged process access without revealing broader filesystem permissions. A service may create an anonymous in-memory file and transfer it to another process.&lt;/p&gt;&#xA;&lt;p&gt;Sending the integer value of a file descriptor does not solve this problem. File descriptor numbers are meaningful only inside one process&amp;rsquo;s descriptor table. Descriptor &lt;code&gt;7&lt;/code&gt; in one process can refer to a socket while descriptor &lt;code&gt;7&lt;/code&gt; in another process refers to an unrelated file.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
