<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Process Identity on Nalar</title>
    <link>https://nalar.dev/tags/process-identity/</link>
    <description>Recent content in Process Identity 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/process-identity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pidfds Turn Process Identity Into a Stable Kernel Reference</title>
      <link>https://nalar.dev/pidfds-turn-process-identity-into-a-stable-kernel-reference/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/pidfds-turn-process-identity-into-a-stable-kernel-reference/</guid>
      <description>&lt;p&gt;A supervisor records PID 1842 for a worker, waits for an asynchronous event, then sends a signal. Between those operations the worker can exit, be reaped, and its numeric PID can later identify another process. The number still looks valid, but the identity it denotes has changed.&lt;/p&gt;&#xA;&lt;p&gt;Linux pidfds move this class of process control away from repeated numeric lookup. A PID file descriptor refers to a particular process, giving userspace a kernel-held reference that can be passed to interfaces such as &lt;code&gt;pidfd_send_signal()&lt;/code&gt;, polling APIs, and, under additional permission checks, &lt;code&gt;pidfd_getfd()&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
